[kernel-xen] Issue Booting DomU's from certain hardware.
Steven Haigh
netwiz at crc.id.au
Sat Sep 29 14:00:32 EST 2012
Further to this, I've started up a test DomU running Debian 6.0.5 as a
test using the instructions here:
http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer#Netboot_installation
Interestingly, I'm getting this as part of the install:
[ 122.818668] kernel BUG at
/build/buildd-linux-2.6_2.6.32-45-amd64-FcX7RM/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/sysfs/group.c:65!
[ 122.818679] invalid opcode: 0000 [#1] SMP
───────────────────────────────┘
[ 122.818687] last sysfs file: /sys/devices/virtual/bdi/202:0/uevent
[ 122.818693] CPU 0
[ 122.818699] Modules linked in: xen_blkfront(+) thermal_sys evdev
xen_netfront
[ 122.818714] Pid: 16, comm: xenwatch Tainted: G W
2.6.32-5-amd64 #1
[ 122.818721] RIP: e030:[<ffffffff81141dd7>] [<ffffffff81141dd7>]
internal_create_group+0x28/0x15a
[ 122.818732] RSP: e02b:ffff88003fe29d30 EFLAGS: 00010246
[ 122.818739] RAX: 00000000ffffffef RBX: ffff8800022cbc00 RCX:
ffffffff8121f7e2
[ 122.818748] RDX: ffffffff8149ad40 RSI: 0000000000000000 RDI:
ffff8800022cbc68
[ 122.818755] RBP: ffff8800022cbc00 R08: 0000000000000003 R09:
ffffffff8147ac20
[ 122.818763] R10: ffff88003fdb2660 R11: 00000000000003c0 R12:
ffff880001c988d0
[ 122.818775] R13: ffff8800022cbc68 R14: ffff88003fdea000 R15:
ffffffff8149ad40
[ 122.818785] FS: 00007f6b139d66e0(0000) GS:ffff880004a7e000(0000)
knlGS:0000000000000000
[ 122.818794] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 122.818800] CR2: 00007f212d04d310 CR3: 000000003c3ca000 CR4:
0000000000002660
[ 122.818808] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 122.818815] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[ 122.818823] Process xenwatch (pid: 16, threadinfo ffff88003fe28000,
task ffff88003fdc7100)
[ 122.818831] Stack:
[ 122.818835] 0000000000000001 ffff8800022cbc58 ffff8800022cbc00
ffff8800022cbc00
[ 122.818846] <0> ffff8800022cbc00 ffff880001c988d0 ffff8800022cbc58
ffff88003fdea000
[ 122.818860] <0> 0000000000000000 ffffffff81180e8e 0000000000000000
ffff8800022cbc00
[ 122.818876] Call Trace:
[ 122.818884] [<ffffffff81180e8e>] ? blk_register_queue+0xbe/0xcc
[ 122.818892] [<ffffffff81184c89>] ? add_disk+0xb8/0x108
[ 122.818901] [<ffffffffa000f224>] ? backend_changed+0x44e/0x468
[xen_blkfront]
[ 122.818911] [<ffffffff811f1c8f>] ? xenwatch_thread+0x117/0x14a
[ 122.818918] [<ffffffff81065042>] ? autoremove_wake_function+0x0/0x2e
[ 122.818928] [<ffffffff811f1b78>] ? xenwatch_thread+0x0/0x14a
[ 122.818935] [<ffffffff81064d75>] ? kthread+0x79/0x81
[ 122.818942] [<ffffffff81011baa>] ? child_rip+0xa/0x20
[ 122.818950] [<ffffffff81010d61>] ? int_ret_from_sys_call+0x7/0x1b
[ 122.818958] [<ffffffff8101151d>] ? retint_restore_args+0x5/0x6
[ 122.818966] [<ffffffff8100e22f>] ? xen_restore_fl_direct_end+0x0/0x1
[ 122.818974] [<ffffffff81011ba0>] ? child_rip+0x0/0x20
[ 122.818980] Code: 41 5d c3 41 57 49 89 d7 41 56 41 55 49 89 fd 41 54
55 53 48 83 ec 18 48 85 ff 89 74 24 04 74 0b 85 f6 75 0b 48 83 7f 30 00
75 14 <0f> 0b eb fe 48 83 7f 30 00 bb ea ff ff ff 0f 84 03 01 00 00 49
[ 122.819083] RIP [<ffffffff81141dd7>] internal_create_group+0x28/0x15a
[ 122.819092] RSP <ffff88003fe29d30>
[ 122.819098] ---[ end trace ece08a1b1eae68ad ]---
[ 127.804110] XENBUS: Waiting for devices to initialise: 295s...290s...
To me, this seems like a fault in the Debian kernel. Any other thoughts
from people who might know Debian much better than me?
--
Steven Haigh
Email: netwiz at crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
On 29/09/2012 11:11 AM, Steven Haigh wrote:
> What comes to mind at the moment is that there is an issue with the
> Debian or Fedora kernel that stops them from loading. After Xen shows
> the pygrub menu, the next step is to launch the guest kernel. If this
> fails, then yes, the DomU will crash - which is what seems to be happening.
>
> Can you post your DomU config file from /etc/xen?
>
> What versions of various distros are you using? I'll try to replicate it
> here - but I admit I'm not a Fedora or Debian user...
>
More information about the kernel-xen
mailing list