April 2015 - openSUSE Virtual - openSUSE Mailing Lists

[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