- openSUSE Virtual

Re: [opensuse-virtual] Booting opensuse installer iso as Xen PV DomU drops to grub prompt?
by lyndat3＠your-mail.com 09 Apr '15

09 Apr '15

On Thu, Apr 9, 2015, at 12:50 PM, Charles Arnold wrote: > > Did `zypper in vm-install` miss some dependencies? > > By default vm-install will use libvirt to create VMs. Using the '--use-xl' flag when > starting vm-install will ignore libvirt and just use Xen's 'xl' toolstack directly. > > Also when you were asked, > > Please specify the type of virtualized graphics hardware. > 1: No Graphics Support > 2: Paravirtualized Graphics Adapter > [2] > > > You should select '1' here and it won't start a graphical installation (should run in the > same window as vm-install is running). vm-install --use-xl Gathering settings... Please specify the type of operating system that will run within the virtual machine. This defines many defaults, and helps decide how to start paravirtualized operating systems. Press 'q' or the Escape key to exit. 1: Novell Open Enterprise Server 2 (Linux) 2: Novell Open Enterprise Server 2 (NetWare) 3: Novell Open Enterprise Server 11 4: Other operating system 5: PXE 6: RedHat (other) 7: RedHat Enterprise Linux 3 8: RedHat Enterprise Linux 4 9: RedHat Enterprise Linux 5 10: RedHat Enterprise Linux 6 11: RedHat Enterprise Linux 7 12: Relax and Recover 13: SUSE (other) 14: SUSE Linux Enterprise Desktop 10 15: SUSE Linux Enterprise Desktop 11 16: SUSE Linux Enterprise Desktop 12 17: SUSE Linux Enterprise Server 8 18: SUSE Linux Enterprise Server 9 19: SUSE Linux Enterprise Server 10 20: SUSE Linux Enterprise Server 11 21: SUSE Linux Enterprise Server 12 22: Solaris 9 and older 23: Solaris 10 24: Ubuntu 10 (Lucid Lynx, Maverick Meerkat) 25: Ubuntu 11 (Natty Narwhal, Oneiric Ocelot) 26: Ubuntu 12 (Precise Pangolin) 27: Ubuntu (other) 28: Windows 8 29: Windows 8 (x64) 30: Windows (other) 31: Windows (other, x64) 32: Windows NT 33: Windows Server 2008 34: Windows Server 2008 (x64) 35: Windows Server 2012 (x64) 36: Windows Vista, Windows 7 37: Windows Vista, Windows 7 (x64) 38: Windows XP, 2000, 2003 39: Windows XP, 2003 (x64) 40: openSUSE 41: openSUSE 11 42: openSUSE 12 43: openSUSE 13 [43] > Virtual machines can use paravirtualization or full virtualization. Paravirtualization is faster but requires operating system support. Full virtualization runs a broader range of operating systems but requires hardware support. Which do you prefer? 1: Full virtualization 2: Paravirtualization [2] > PXE Boot (Y / N) [N] > Please choose a name for the virtual machine. [opensuse13] > Description > Specify the amount of memory and number of processors to allocate for the VM. Initial Memory [768] > Maximum Memory [768] > Virtual Processors [1] > Please specify the type of virtualized graphics hardware. 1: No Graphics Support 2: Paravirtualized Graphics Adapter [2] > 1 <------------------------------------------------ Virtual Disks: (None) Do you want to add another virtual disk? (Y / N) [Y] > Create a virtual disk based on a device (CD or other block device), an existing image file (ISO), or a new file. Specify a device by its device node, such as /dev/cdrom, not its mount point. What type of virtual disk do you want to add? 1: CD-ROM or DVD 2: Hard Disk [2] > 2 Where will the virtual disk physically reside? [/var/lib/xen/images/opensuse13/xvda] > Size (GB) [8.0] > 1 Create a sparse image file for the virtual disk? (Y / N) [Y] > Virtual Disks: 1.0 GB Hard Disk (file:/var/lib/xen/images/opensuse13/xvda) Do you want to add another virtual disk? (Y / N) [N] > y Create a virtual disk based on a device (CD or other block device), an existing image file (ISO), or a new file. Specify a device by its device node, such as /dev/cdrom, not its mount point. What type of virtual disk do you want to add? 1: CD-ROM or DVD 2: Hard Disk [2] > 1 Where will the virtual disk physically reside? [/var/lib/xen/images/opensuse13/xvdb] > /home/lt/work/openSUSE-13.2-DVD-x86_64.iso Virtual Disks: 1.0 GB Hard Disk (file:/var/lib/xen/images/opensuse13/xvda) 4.4 GB CD-ROM or DVD (file:/home/lt/work/openSUSE-13.2-DVD-x86_64.iso) Do you want to add another virtual disk? (Y / N) [N] > Network Adapters (None) Do you want to add another virtual network adapter? (Y / N) [Y] > Network Adapters Paravirtualized; Randomly generated MAC address Do you want to add another virtual network adapter? (Y / N) [N] > Specify the bootable virtual disk (often labeled as Disk 1) or the network installation source URL. Each CD, DVD, or ISO image required for installation must be added as a virtual disk. 1: Network URL (ftp://, http://, nfs://, smb://) 2: Virtual Disk (4.4 GB CD-ROM or DVD (file:/home/lt/work/openSUSE-13.2-DVD-x86_64.iso)) [1] > 2 Some operating systems support automating the installation by specifying a URL or file(s). Select a directory to include multiple files. AutoYaST file > Some operating systems accept additional arguments, used to customize the installation or boot process. Additional Arguments > Preparing to start the installation... Installing... Error: [Errno 2] No such file or directory Performing post-installation checks... Error: [Errno 2] No such file or directory: '/var/lib/xen/images/opensuse13/xvda' Exception OSError: (2, 'No such file or directory', '/etc/xen/vm/opensuse13.xml') in <bound method Job.__del__ of <vminstall.job.Job object at 0x7fbd5dc18210>> ignored Where ls -al /var/lib/xen/images/opensuse13 /etc/xen/vm/ /etc/xen/vm/: total 8.0K drwxr-xr-x 2 root root 4.0K Apr 9 13:03 ./ drwx------ 6 root root 4.0K Apr 9 06:19 ../ /var/lib/xen/images/opensuse13: total 8.0K drwxr-xr-x 2 root root 4.0K Apr 9 13:03 ./ drwx------ 3 root root 4.0K Apr 9 12:28 ../ The script doesn't create/dd the xvda HD? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 5

Re: [opensuse-virtual] Booting opensuse installer iso as Xen PV DomU drops to grub prompt?
by Charles Arnold 09 Apr '15

09 Apr '15

>>> On 4/9/2015 at 01:41 PM, <lyndat3(a)your-mail.com> wrote: >> > It is much easier to use this tool graphically. Does your host not have > graphics or are you ssh'ing without X forwarding? >> >> No, no graphics. > > > I installed xterm and it's dependencies. > > When I ssh -X into the server, and exec 'xterm', it opens graphically > locally. So that works. > > But when I exec vm-install, I get the error > > vm-install > libvirt: XML-RPC error : Failed to connect socket to > '/var/run/libvirt/libvirt-sock': No such file or directory > Error: Failed to open a connection to libvirt. Please verify the libvirt > daemon is running. > > Did `zypper in vm-install` miss some dependencies? By default vm-install will use libvirt to create VMs. Using the '--use-xl' flag when starting vm-install will ignore libvirt and just use Xen's 'xl' toolstack directly. Also when you were asked, Please specify the type of virtualized graphics hardware. 1: No Graphics Support 2: Paravirtualized Graphics Adapter [2] > You should select '1' here and it won't start a graphical installation (should run in the same window as vm-install is running). - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

Re: [opensuse-virtual] Booting opensuse installer iso as Xen PV DomU drops to grub prompt?
by lyndat3＠your-mail.com 09 Apr '15

09 Apr '15

> At this point you should add a second disk that is the ISO file you want to use as > an installation source. Select '1: CD-ROM or DVD' and then enter the full path to the ISO file. ... > If you added an ISO above, it will show up here as [2] and you can select it. That's it. The question suggested PHYSICAL cd/dvd to me; hadn't thought to add the iso there. Specify the bootable virtual disk (often labeled as Disk 1) or the network installation source URL. Each CD, DVD, or ISO image required for installation must be added as a virtual disk. 1: Network URL (ftp://, http://, nfs://, smb://) 2: Virtual Disk (4.4 GB CD-ROM or DVD (file:/home/lt/work/openSUSE-13.2-DVD-x86_64.iso)) [1] > 2 which gets past THAT error. But fails later Preparing to start the installation... Installing... Failed to display the VM's console. Please connect a viewer manually. Performing post-installation checks... Error: No kernel was found. The installation may have failed. > It is much easier to use this tool graphically. Does your host not have graphics or are you ssh'ing without X forwarding? No, no graphics. It really should be possible to read good docs and install on a minimal install without installing a graphical environment. LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 1

Re: [opensuse-virtual] Booting opensuse installer iso as Xen PV DomU drops to grub prompt?
by lyndat3＠your-mail.com 09 Apr '15

09 Apr '15

On Thu, Apr 9, 2015, at 10:47 AM, Charles Arnold wrote: > > What's missing from the config ^^ to get past the grub prompt and 'start' > > the installer? > > Given that you are using 'xl' to create your VM (instead of libvirt's virsh/virt-install) you might > want to try using 'vm-install --use-xl' and step through the vm-install's setup and see if > that creates the type of VM you need. The configuration file created by vm-install will be > found in /etc/xen/vm/. Vm-install will create an install time configuration file that will later > be replaced by a runtime version when the installation is complete. I prefer to use Xen's default/included xl toolstack to keep my install minimal, and it's likely best supported. Installing 'vm-install' further requires The following 34 NEW packages are going to be installed: atftp cyrus-sasl cyrus-sasl-digestmd5 dbus-1-python girepository-1_0 gnutls kdump libavahi-client3 libavahi-common3 libcacard0 libesmtp libfreebl3 libgirepository-1_0-1 libgnutls28 libhogweed2 libnettle4 libsnappy1 libsoftokn3 libvirt-client libvirt-python makedumpfile mozilla-nss mozilla-nss-certs python-bottle python-CherryPy python-gobject python-libxml2 python-pycurl python-simplejson python-urlgrabber qemu-tools udhcp usbutils vm-install which is unfortunate, but if it's required to get an answer here, ok. Creating a vm with it fails vm-install --use-xl Gathering settings... Please specify the type of operating system that will run within the virtual machine. This defines many defaults, and helps decide how to start paravirtualized operating systems. Press 'q' or the Escape key to exit. 1: Novell Open Enterprise Server 2 (Linux) 2: Novell Open Enterprise Server 2 (NetWare) 3: Novell Open Enterprise Server 11 4: Other operating system 5: PXE 6: RedHat (other) 7: RedHat Enterprise Linux 3 8: RedHat Enterprise Linux 4 9: RedHat Enterprise Linux 5 10: RedHat Enterprise Linux 6 11: RedHat Enterprise Linux 7 12: Relax and Recover 13: SUSE (other) 14: SUSE Linux Enterprise Desktop 10 15: SUSE Linux Enterprise Desktop 11 16: SUSE Linux Enterprise Desktop 12 17: SUSE Linux Enterprise Server 8 18: SUSE Linux Enterprise Server 9 19: SUSE Linux Enterprise Server 10 20: SUSE Linux Enterprise Server 11 21: SUSE Linux Enterprise Server 12 22: Solaris 9 and older 23: Solaris 10 24: Ubuntu 10 (Lucid Lynx, Maverick Meerkat) 25: Ubuntu 11 (Natty Narwhal, Oneiric Ocelot) 26: Ubuntu 12 (Precise Pangolin) 27: Ubuntu (other) 28: Windows 8 29: Windows 8 (x64) 30: Windows (other) 31: Windows (other, x64) 32: Windows NT 33: Windows Server 2008 34: Windows Server 2008 (x64) 35: Windows Server 2012 (x64) 36: Windows Vista, Windows 7 37: Windows Vista, Windows 7 (x64) 38: Windows XP, 2000, 2003 39: Windows XP, 2003 (x64) 40: openSUSE 41: openSUSE 11 42: openSUSE 12 43: openSUSE 13 [43] > Virtual machines can use paravirtualization or full virtualization. Paravirtualization is faster but requires operating system support. Full virtualization runs a broader range of operating systems but requires hardware support. Which do you prefer? 1: Full virtualization 2: Paravirtualization [2] > PXE Boot (Y / N) [N] > Please choose a name for the virtual machine. [opensuse13] > Description > Specify the amount of memory and number of processors to allocate for the VM. Initial Memory [768] > Maximum Memory [768] > Virtual Processors [1] > Please specify the type of virtualized graphics hardware. 1: No Graphics Support 2: Paravirtualized Graphics Adapter [2] > Virtual Disks: (None) Do you want to add another virtual disk? (Y / N) [Y] > Create a virtual disk based on a device (CD or other block device), an existing image file (ISO), or a new file. Specify a device by its device node, such as /dev/cdrom, not its mount point. What type of virtual disk do you want to add? 1: CD-ROM or DVD 2: Hard Disk [2] > 2 Where will the virtual disk physically reside? [/var/lib/xen/images/opensuse13/xvda] > Size (GB) [8.0] > 1 Create a sparse image file for the virtual disk? (Y / N) [Y] > Virtual Disks: 1.0 GB Hard Disk (file:/var/lib/xen/images/opensuse13/xvda) Do you want to add another virtual disk? (Y / N) [N] > Network Adapters (None) Do you want to add another virtual network adapter? (Y / N) [Y] > Network Adapters Paravirtualized; Randomly generated MAC address Do you want to add another virtual network adapter? (Y / N) [N] > Specify the bootable virtual disk (often labeled as Disk 1) or the network installation source URL. Each CD, DVD, or ISO image required for installation must be added as a virtual disk. 1: Network URL (ftp://, http://, nfs://, smb://) [1] > Type the install URL: > file:/home/lt/work/openSUSE-13.2-DVD-x86_64.iso Some operating systems support automating the installation by specifying a URL or file(s). Select a directory to include multiple files. AutoYaST file > Some operating systems accept additional arguments, used to customize the installation or boot process. Additional Arguments > ERROR No installation source was defined. Error: No installation source was defined. Please correct the error and try again. ======================================== Please specify the type of operating system that will run within the virtual machine. This defines many defaults, and helps decide how to start paravirtualized operating systems. Press 'q' or the Escape key to exit. 1: Novell Open Enterprise Server 2 (Linux) 2: Novell Open Enterprise Server 2 (NetWare) 3: Novell Open Enterprise Server 11 4: Other operating system 5: PXE 6: RedHat (other) 7: RedHat Enterprise Linux 3 8: RedHat Enterprise Linux 4 9: RedHat Enterprise Linux 5 10: RedHat Enterprise Linux 6 11: RedHat Enterprise Linux 7 12: Relax and Recover 13: SUSE (other) 14: SUSE Linux Enterprise Desktop 10 15: SUSE Linux Enterprise Desktop 11 16: SUSE Linux Enterprise Desktop 12 17: SUSE Linux Enterprise Server 8 18: SUSE Linux Enterprise Server 9 19: SUSE Linux Enterprise Server 10 20: SUSE Linux Enterprise Server 11 21: SUSE Linux Enterprise Server 12 22: Solaris 9 and older 23: Solaris 10 24: Ubuntu 10 (Lucid Lynx, Maverick Meerkat) 25: Ubuntu 11 (Natty Narwhal, Oneiric Ocelot) 26: Ubuntu 12 (Precise Pangolin) 27: Ubuntu (other) 28: Windows 8 29: Windows 8 (x64) 30: Windows (other) 31: Windows (other, x64) 32: Windows NT 33: Windows Server 2008 34: Windows Server 2008 (x64) 35: Windows Server 2012 (x64) 36: Windows Vista, Windows 7 37: Windows Vista, Windows 7 (x64) 38: Windows XP, 2000, 2003 39: Windows XP, 2003 (x64) 40: openSUSE 41: openSUSE 11 42: openSUSE 12 43: openSUSE 13 [43] > q There's no config file created ls -al /etc/xen/vm total 8.0K drwxr-xr-x 2 root root 4.0K Apr 8 16:16 ./ drwx------ 6 root root 4.0K Apr 9 06:19 ../ I'll guess it's this ERROR No installation source was defined. Error: No installation source was defined. Please correct the error and try again. How is the installer iso supposed to be passed to the vm-install script if not as a file:/ ? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

[opensuse-virtual] Booting opensuse installer iso as Xen PV DomU drops to grub prompt?
by lyndat3＠your-mail.com 09 Apr '15

09 Apr '15

I'm trying to launch the openSUSE 13.2 installer in a Xen DomU via pvgrub2. It looks like the installer iso contains all the Xen PV pieces. mount -o loop openSUSE-13.2-DVD-x86_64.iso /mnt/iso cd /mnt/iso find . | grep xen | egrep "/xen|/initrd|/vmlinuz|/grub|/kernel" ./boot/x86_64/initrd-xen ./boot/x86_64/vmlinuz-xen ./suse/x86_64/grub2-x86_64-xen-2.02~beta2-20.5.1.x86_64.rpm ./suse/x86_64/kernel-xen-3.16.6-2.1.x86_64.rpm ./suse/x86_64/kernel-xen-devel-3.16.6-2.1.x86_64.rpm ./suse/x86_64/xen-4.4.1_06-3.3.x86_64.rpm ./suse/x86_64/xen-doc-html-4.4.1_06-3.3.x86_64.rpm ./suse/x86_64/xen-kmp-default-4.4.1_06_k3.16.6_2-3.3.x86_64.rpm ./suse/x86_64/xen-kmp-desktop-4.4.1_06_k3.16.6_2-3.3.x86_64.rpm ./suse/x86_64/xen-libs-4.4.1_06-3.3.x86_64.rpm ./suse/x86_64/xen-tools-4.4.1_06-3.3.x86_64.rpm ./suse/x86_64/xen-tools-domU-4.4.1_06-3.3.x86_64.rpm Using this for the Guest config at the Dom0 cat /home/lt/work/test.cfg boot = 'd' disk = ['file:/home/lt/work/openSUSE-13.2-DVD-x86_64.iso,hdd:cdrom,r', ] kernel = "/usr/lib/grub2/x86_64-xen/grub.xen" name = 'test' netif = 'yes' sdl = 0 stdvga = 1 vif = [ 'mac=00:16:3E:01:01:01, bridge=br0, vifname=vif0',] vnc = 0 creating the Guest xl create -c ./test.cfg just drops to a "grub>" prompt. What's missing from the config ^^ to get past the grub prompt and 'start' the installer? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

[opensuse-virtual] How to conditionally configure & use bridge interface only when booting to Xen?
by lyndat3＠your-mail.com 09 Apr '15

09 Apr '15

I have a server with a single ethernet interface, eno1. When booting to kernel-default, the interface is configured in /etc/sysconfig/network/ifcfg-eno1 and gets brought up by the wicked networking stack If I switch to Xen, booting to kernel-xen, I can bring up the Dom0 in this configuration too. But for PV DomUs, I need a bridge interface to pass in vif=[...] I know how to create & configure the bridge interface (/etc/sysconfig/network/ifcfg-br0) to 'take over' eno1 I can't figure out how to create & use the bridge only conditionally -- in the Xen-boot case. In other words, if boot to non-Xen, use intfc "eno1" and, if boot to Xen, use intfc "br0" instead On my previous servers I'd use if-up & if-down scripts to handle it. The up/down scripts don't seem to work with the opensuse wicked stack. How do you handle conditional network configuration with wicked, depending on which boot environment -- Xen or non-Xen -- you're booting to? IIUC the advice has been to use opensuse networking config to setup the interfaces. To do this ^^ do you have to step outside the OS config? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

[opensuse-virtual] where do Xen 4.5 boot-time options go in opensuse 13.2 -- with no rc.local?
by lyndat3＠your-mail.com 08 Apr '15

08 Apr '15

Xen's "best practices" http://wiki.xenproject.org/wiki/Xen_Project_Best_Practices instruct that to make changes to the Dom0 scheduling weight default (=256) persistent "You can place the "xm sched-credit" to rc.local or other script that is executed late in the boot process. Make sure the command is executed after xend is started, since the xm command needs to talk to xend." Opensuse uses systemd, there's no rc.local, and IIUC no xend in Xen 4.5+. Where should a change to the default setting like xl sched-credit -d Domain-0 -w 512 be made? There's /usr/lib/systemd/system/after-local.service -> /etc/init.d/after.local but any entries there would have to detect Xen and be Xen-specific, not firing if booting to non-Xen. LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 1

Re: [opensuse-virtual] Support for pvgrub2 Xen guest bootloader?
by lyndat3＠your-mail.com 07 Apr '15

07 Apr '15

Hi > With openSUSE 13.2 and SLE12 the installation tools have begun using > grub.xen (part of the grub2-x86_64-xen package) to boot these newer > VMs. The tools also continue to use pygrub on older VMs but this will > likely change in the future. grub.xen will boot both grub and grub2 based > VMs. It will also boot VMs that use BTRFS as the root filesystem which > Xen's current version of pvgrub does not understand (nor does pygrub). That's useful info. I have these installed rpm -qa | grep -i grub | sort grub2-2.02~beta2-20.5.1.x86_64 grub2-branding-openSUSE-13.2-3.6.1.noarch grub2-i386-pc-2.02~beta2-20.5.1.x86_64 grub2-snapper-plugin-2.02~beta2-20.5.1.noarch grub2-x86_64-efi-2.02~beta2-20.5.1.x86_64 grub2-x86_64-xen-2.02~beta2-20.5.1.x86_64 The Dom0 is booted uname -rm 3.19.3-1.gf10e7fc-xen x86_64 The Dom0 boot loader IS grub2, but I'm on a UEFI system. Xen's booted using the currently needed chainloader workaround. I'm not sure if that means I'm using grub2-x86_64-efi or grub2-x86_64-xen. Since I don't have a specific 'grub.xen' mentioned, are either of those all I need to boot the grub2-based VMs? More to the point, what specifically do I need to do to USE the pvgrub2 capability to boot a grub2-based, ext4 using the guest's own kernel? And in opensuse, does all that ^^ still work for either opensuse DomUs, using the opensuse-specific kernel-xen backport, OR other-OSs using unmodified, pv-ops capable kernels? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

[opensuse-virtual] Support for pvgrub2 Xen guest bootloader?
by lyndat3＠your-mail.com 07 Apr '15

07 Apr '15

IIUC pvgrub Xen guest loading was developed to address some of the security shortcomings of pygrub. opensuse had rejected request(s) to provide 'pvgrub' PV Grub support in opensuse https://features.opensuse.org/306592 'pygrub' has an advantage of being able to boot a grub2 guest; 'pvgrub' does not. 'pvgrub2' has been developed to address that; it both boots grub2 guests and maintains the security advantages over pygrub. Using Grub 2 as a bootloader for Xen PV guests https://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen… In that post, Ian Campbell addreses pvgrub2 availability/support in Debian/Jessie, and states I’m not aware of any other distributions which have integrated grub2 support for Xen. I’d be glad to be corrected or equally happy to help advise on any integration efforts. Does opensuse provide pvgrub2 for Xen guest bootloading, and where is it documented? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

[opensuse-virtual] booting to Xen 4.5 on Grub2+UEFI gets caught in systemd journal loop?
by lyndat3＠your-mail.com 06 Apr '15

06 Apr '15

I'm working on booting Xen 4.5 on an opensuse 13.2 GRUB2+UEFI box. The system fully boots to non-Xen, kernel-default. In the Xen case, Until Xen 4.6 comes available, I have grub2 chainloading xen.efi. The .efi is found, Xen loads, and hands off to the kernel-xen boot process. It gets fairly far then gets caught in a systemd-journal loop. Output at serial console is Xen 4.5.0_03-361 (c/s ) EFI loader Using configuration file 'xen.cfg' vmlinuz-xen: 0x000000008c0d1000-0x000000008c5aaf10 initrd-xen: 0x000000008b346000-0x000000008c0d0c78 0x0000:0x00:0x19.0x0: ROM: 0x10000 bytes at 0x92963018 0x0000:0x04:0x00.0x0: ROM: 0x8000 bytes at 0x92953018 0x0000:0x10:0x00.0x0: ROM: 0x10800 bytes at 0x9293b018 Xen 4.5.0_03-361 (XEN) Xen version 4.5.0_03-361 (abuild(a)suse.de) (gcc (SUSE Linux) 4.8.3 20140627 [gcc-4_8-branch revision 212064]) debug=n Mon Mar 16 16:14:15 UTC 2015 ... (XEN) [2015-04-06 10:45:44] Xen is relinquishing VGA console. (XEN) [2015-04-06 10:45:44] *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) [2015-04-06 10:45:44] Freed 316kB init memory. [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.19.3-1.gf10e7fc-xen (geeko@buildhost) (gcc version 4.8.3 20141208 [gcc-4_8-branch revision 218481] (SUSE Linux) ) #1 SMP Thu Mar 26 17:34:34 UTC 2015 (f10e7fc) ... [ 218.221315] systemd[1]: Accepted new private connection. [ 218.238825] systemd[1]: Got message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/agent interface=org.freedesktop.systemd1.Agent member=Released cookie=1 reply_cookie=0 error=n/a [ 218.238841] systemd-journald[896]: Entry is too big with 8 properties and 16924204553027465025 bytes, ignoring. [ 218.331936] systemd[1]: Got disconnect on private connection. [ 240.000517] systemd[1]: Got notification message for unit systemd-journald.service [ 240.024839] systemd[1]: systemd-journald.service: Got notification message from PID 896 (WATCHDOG=1...) ... [ 478.806639] systemd[1]: systemd-journald.service: got WATCHDOG=1 [ 478.826279] systemd[1]: Got notification message for unit systemd-journald.service [ 478.850591] systemd[1]: systemd-journald.service: Got notification message from PID 896 (WATCHDOG=1...) [ 478.882226] systemd[1]: systemd-journald.service: got WATCHDOG=1 ... [ 820.076223] systemd[1]: Got notification message for unit systemd-journald.service [ 820.100546] systemd[1]: systemd-journald.service: Got notification message from PID 896 (WATCHDOG=1...) [ 820.132191] systemd[1]: systemd-journald.service: got WATCHDOG=1 Notice the ridiculously large 'bytes' value in [ 218.238841] systemd-journald[896]: Entry is too big with 8 properties and 16924204553027465025 bytes, ignoring. Usually I'd use systemd journal & serial console to debug this. But it looks like those are the problem here. How do I get more detail out of logs to figure out what's causing this problem? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0