[opensuse-virtual] heads up, kernel/stable upgrade -> 4.7.x breaks Xen 4.7 Dom0 boot; Xen-only hardware crash
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@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Am 19.08.2016 um 12:11 schrieb John Connett:
Any other useful information that I could supply?
Probably the full boot log including xen and dom0 output, and xen booted with loglvl=all. Olaf -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 19.08.16 at 12:11, <jrc@skylon.demon.co.uk> wrote: 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?
https://bugzilla.kernel.org/show_bug.cgi?id=153081 Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 19/08/16 13:19, Jan Beulich wrote:
On 19.08.16 at 12:11, <jrc@skylon.demon.co.uk> wrote: 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?
Many thanks. Looks like I'll have to wait for the update (unless there is some way to produce a non-empty ESRT?). -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 19/08/16 15:09, John Connett wrote:
On 19/08/16 13:19, Jan Beulich wrote:
On 19.08.16 at 12:11, <jrc@skylon.demon.co.uk> wrote: 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?
Many thanks. Looks like I'll have to wait for the update (unless there is some way to produce a non-empty ESRT?).
From https://bugzilla.kernel.org/show_bug.cgi?id=153081
lssl 2016-09-09 18:29:46 UTC
same for 4.7.3.
Is this going to be backported to 4.7 branch by upstream?
It's not being addressed by the distro.
Should we just write off using "stable" kernel 4.7 branch as WONTFIX, and wait for 4.8?
Is there a Tumbleweed package combination that I can use as a work around? I found kernel-default-4.8.rc5-2.1.gd38eb05.x86_64 in the Kernel:HEAD repository but couldn't find matching xen-4.8??? and xen-tools-4.8??? packages.
participants (3)
-
Jan Beulich -
John Connett -
Olaf Hering