September 2016 - openSUSE Virtual - openSUSE Mailing Lists

[opensuse-virtual] heads up, kernel/stable upgrade -> 4.7.x breaks Xen 4.7 Dom0 boot; Xen-only hardware crash
by John Connett 10 Sep '16

10 Sep '16

I'm also experiencing this on openSUSE Tumbleweed (20160817) (x86_64): kernel-default-4.7.0-2.2.x86_64 xen-4.7.0_10-1.1.x86_64 xen-tools-4.7.0_10-1.1.x86_64 System updated today with zypper up then Xen installed with: YaST -> Virtualization -> Install Hypervisor and Tools then selecting Xen server and Xen tools. Non-Xen boot working. Xen boot crashes. Below is an excerpt from the console log. Is there a Bugzilla bug number for this? Any other useful information that I could supply? ---------------------------------------------------------------------- [ 0.000000] bootconsole [xenboot0] enabled [ 0.000000] efi: EFI_MEMMAP is not enabled. [ 0.000000] esrt: ESRT header is not in the memory map. (XEN) d0v0: unhandled page fault (ec=0000) (XEN) Pagetable walk from 0000000000000018: (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S: fault at ffff82d08023098a entry.o#create_bounce_frame+0x137/0x146 (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.7.0_10-1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff81f6374c>] (XEN) RFLAGS: 0000000000000246 EM: 1 CONTEXT: pv guest (d0v0) (XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000100000000 (XEN) rdx: 000000081e600000 rsi: ffffffff81efb280 rdi: 000000081e600000 (XEN) rbp: 0000000000000000 rsp: ffffffff81e03e50 r8: 0000000000000200 (XEN) r9: 0000000000000000 r10: 0000000000007ff0 r11: 0000000000000067 (XEN) r12: 0000000000000000 r13: ffffffff81e03f28 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 0000000080050033 cr4: 00000000001526e0 (XEN) cr3: 0000000801e06000 cr2: 0000000000000018 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff81e03e50: (XEN) 0000000100000000 0000000000000067 0000000000000000 ffffffff81f6374c (XEN) 000000010000e030 0000000000010046 ffffffff81e03e98 000000000000e02b (XEN) ffffffff820e2ce0 0000000001000000 0000000001290000 0000000000000000 (XEN) ffffffff81e03f28 ffffffff81f4d940 ffffffff8118b419 ffffffff00000010 (XEN) ffffffff81e03f28 ffffffff81e03ee0 000000000000001a 0000000000000000 (XEN) ffffffffffffffff 0000000000000000 ffffffff81fe9920 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff81f42b92 ffffffff81ff62e0 (XEN) ffffffff81e03f68 ffffffff81e03f64 0000000000000000 0000000000000000 (XEN) ffffffff81f486b1 000306a900000000 0000000100100800 0300000100000032 (XEN) 0000000000000005 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0f00000060c0c748 ccccccccccccc305 (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 4

[opensuse-virtual] leap422 - no /proc/sys/xen/independent_wallclock ?
by Per Jessen 09 Sep '16

09 Sep '16

I don't see this in Leap422. Has it disappeared or become superfluous? /Per -- Per Jessen, Zürich (18.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- 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] should ntp be governing the clock in a guest system?
by Per Jessen 05 Sep '16

05 Sep '16

Continued from opensuse-factory: > >>>> Probably other virtualization technology have the same issue, do > >>>> not use ntp. I do not know for certain. > >>> > >>> With xen, my guests run ntpd and have xen.independent_wallclock=1. > >> > >> And both host and guest try to adjust the speed of the mother board > >> hardware clock chip? (not the bios clock, that's a very different > >> one). > > > > No, only the Dom0 does that. The guests are independent when you > > use xen.independent_wallclock=1. > > >http://www.novell.com/documentation/vmserver/config_options/data/b9qzhq5.ht… > > But if you run the ntp daemon on guests, it tries to adjust the speed > of the clock there. That's how it works. Of course, that's what you want it to do. You want the guest clock synchronized. It would appear to be a good idea to have ntp on the xen Dom0 govern the clock for all the guests, but in my experience systemd does not like that. I looked into in March 2015 when I was virtualising some systems, and found the Novell page above. The Xen FAQ: https://wiki.xen.org/wiki/Xen_FAQ_DomU also recommends running ntp in each DomU. Finally, Werner Flamme wrote: > When you install SAP systems on top of Xenified VMs, there is the > recommendation to do the latter: disable the sync and run a separate > ntpd in the DomU. This is also a recommendation for VMs inside a > VMWare environment - the problem ist the same there. Back in March last year I did ask what the typical practice was, but noone had any suggestions. -- Per Jessen, Zürich (25.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 8