Host is a f8 dom0 running xen-3.1.2-5.fc8 and kernel 2.6.21.7-5.fc8xen.x86_64. I updated a f10 guest domU to the latest kernel update 2.6.27.30-170.2.82.fc10.x86_64 and rebooted it without problem. I updated a f11 domU to kernel-2.6.30.5-43.fc11.x86_64 and the guest crashes after grub. Cracking open the image and setting grub back to kernel-2.6.29.6-217.2.16.fc11.x86_64 got me up and running. xm dmesg shows (XEN) traps.c:405:d117 Unhandled general protection fault fault/trap [#13] in domain 117 on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 117 (vcpu#0) crashed on cpu#3: (XEN) ----[ Xen-3.1.4 x86_64 debug=n Not tainted ]---- (XEN) CPU: 3 (XEN) RIP: e033:[<ffffffff813cda87>] (XEN) RFLAGS: 0000000000000282 CONTEXT: guest (XEN) rax: 000000008000c068 rbx: 000000000000c000 rcx: 0000000000000068 (XEN) rdx: 0000000000000cf8 rsi: 0000000000000018 rdi: 0000000000000000 (XEN) rbp: ffffffff8172de48 rsp: ffffffff8172dde0 r8: 0000000000000068 (XEN) r9: ffffffff8172de60 r10: ffffffff8172de68 r11: 00000000ffffffff (XEN) r12: ffffffff81697500 r13: ffffffff8172df78 r14: ffffffffffffffff (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000006f0 (XEN) cr3: 00000002f53fe000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff8172dde0: (XEN) 0000000000000068 00000000ffffffff 0000000000000000 ffffffff813cda87 (XEN) 000000010000e030 0000000000010082 ffffffff8172de28 000000000000e02b (XEN) ffffffff813cda4d ffffffff8172de88 965f5967f03da9c3 ffffffff8100a7ed (XEN) ffffffff81722b80 ffffffff8172de88 ffffffff8148f7c1 00020f5103000800 (XEN) 0000000000000000 0000302800000000 965f5967f03da9c3 ffffffffffffffff (XEN) 0000000000000018 ffffffff8172dea8 ffffffff81760bc2 ffffffff8179ca10 (XEN) 0000000000000000 ffffffff8172df58 ffffffff8175ce66 0000000000000000 (XEN) 965f5967f03da9c3 ffffffff8172dee8 ffffffff8179ca10 0000000000000000 (XEN) 0000000000000000 ffffffffffffffff 0000000000000000 ffffffff8172df58 (XEN) ffffffff81495adb ffffffff00000010 ffffffff8172df68 ffffffff8172df28 (XEN) 965f5967f03da9c3 00000000a1b58930 ffffffff8179ca10 0000000000000000 (XEN) 0000000000000000 ffffffffffffffff 0000000000000000 ffffffff8172dfa8 (XEN) ffffffff81757d0b ffffffff8172dfa8 965f5967f03da9c3 ffffffff82226000 (XEN) 0000000000000000 00000000019d0f60 0000000000000000 0000000000000000 (XEN) 0000000000000000 ffffffff8172dfd8 ffffffff817572d0 0000000000000018 (XEN) 0000000000000000 0000000000000000 ffffffff82226000 ffffffff8172dff8 (XEN) ffffffff8175b4e0 0000000000000000 0000000000000000 0000000000000000 (XEN) ffffffff82123000 ffffffff82124000 ffffffff82125000 ffffffff82126000 (XEN) ffffffff82127000 ffffffff82128000 ffffffff82129000 ffffffff8212a000 (XEN) ffffffff8212b000 ffffffff8212c000 ffffffff8212d000 ffffffff8212e000 (XEN) traps.c:405:d118 Unhandled general protection fault fault/trap [#13] in domain 118 on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S
Dale Bewley
2009-Oct-29 21:04 UTC
Re: [Fedora-xen] f11 domU 2.6.30 will not boot on f8 dom0
----- "Dale Bewley" <dlbewley@lib.ucdavis.edu> wrote:> Host is a f8 dom0 running xen-3.1.2-5.fc8 and kernel > 2.6.21.7-5.fc8xen.x86_64. > > I updated a f10 guest domU to the latest kernel update > 2.6.27.30-170.2.82.fc10.x86_64 and rebooted it without problem. > > I updated a f11 domU to kernel-2.6.30.5-43.fc11.x86_64 and the guest > crashes after grub. Cracking open the image and setting grub back to > kernel-2.6.29.6-217.2.16.fc11.x86_64 got me up and running.F11 domU kernel 2.6.30.9-90.fc11.x86_64 does work for me. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3