[Xen-users] During startup of DomU: Kernel panic - not syncing: Out of memory and no killable processes...

[Maik Brauer <maik.brauer@xxxxxxxxxxxxxxx>]

Hi,

during the startup of my DomU I receive the following dump from XEN:

    0.049327] TCP: Hash tables configured (established 2048 bind 2048)

[    0.049334] TCP reno registered

[    0.049388] NET: Registered protocol family 1

[    0.049446] Unpacking initramfs...

[    0.908791] Kernel panic - not syncing: Out of memory and no killable processes...

[    0.908793] 

[    0.908857] Pid: 1, comm: swapper Not tainted 2.6.32-5-xen-amd64 #1

[    0.908862] Call Trace:

[    0.908880]  [<ffffffff8130b7aa>] ? panic+0x86/0x143

[    0.908895]  [<ffffffff8100e635>] ? xen_force_evtchn_callback+0x9/0xa

[    0.908907]  [<ffffffff810bafc7>] ? get_page_from_freelist+0x723/0x767

[    0.908916]  [<ffffffff8102ddc4>] ? pvclock_clocksource_read+0x3a/0x8b

[    0.908929]  [<ffffffff8106d4f7>] ? ktime_get_ts+0x68/0xb2

[    0.908936]  [<ffffffff810b7821>] ? __out_of_memory+0x10f/0x141

[    0.908941]  [<ffffffff810b7993>] ? out_of_memory+0x140/0x172

[    0.908947]  [<ffffffff810bb742>] ? __alloc_pages_nodemask+0x4ec/0x5fe

[    0.908956]  [<ffffffff810e1ad7>] ? alloc_page_interleave+0x2d/0x74

[    0.908962]  [<ffffffff810b574e>] ? grab_cache_page_write_begin+0x55/0x97

[    0.908973]  [<ffffffff81108ac1>] ? simple_write_begin+0x28/0x5d

[    0.908980]  [<ffffffff810b5fc4>] ? generic_file_buffered_write+0x118/0x278

[    0.908986]  [<ffffffff811047e1>] ? mntput_no_expire+0x23/0xee

[    0.908997]  [<ffffffff810b64d5>] ? __generic_file_aio_write+0x25f/0x293

[    0.909003]  [<ffffffff81101d8d>] ? inode_init_always+0x109/0x1aa

[    0.909009]  [<ffffffff810b6562>] ? generic_file_aio_write+0x59/0x9f

[    0.909017]  [<ffffffff810efc4e>] ? do_sync_write+0xce/0x113

[    0.909024]  [<ffffffff81065f86>] ? autoremove_wake_function+0x0/0x2e

[    0.909035]  [<ffffffff811544fd>] ? cap_inode_setattr+0x0/0x3

[    0.909042]  [<ffffffff8100ecf2>] ? check_events+0x12/0x20

[    0.909047]  [<ffffffff811544fd>] ? cap_inode_setattr+0x0/0x3

[    0.909053]  [<ffffffff810f05a0>] ? vfs_write+0xa9/0x102

[    0.909058]  [<ffffffff810f06b5>] ? sys_write+0x45/0x6e

[    0.909066]  [<ffffffff81509a02>] ? do_copy+0x2c/0xdf

[    0.909072]  [<ffffffff815097fb>] ? unpack_to_rootfs+0x1a6/0x381

[    0.909084]  [<ffffffff811a56f7>] ? pci_get_subsys+0x21/0x73

[    0.909090]  [<ffffffff8150a209>] ? populate_rootfs+0x0/0x108

[    0.909096]  [<ffffffff8150a268>] ? populate_rootfs+0x5f/0x108

[    0.909105]  [<ffffffff8152da34>] ? pci_apply_final_quirks+0x1f/0x2b

[    0.909111]  [<ffffffff8100a065>] ? do_one_initcall+0x64/0x174

[    0.909117]  [<ffffffff81508677>] ? kernel_init+0x158/0x1ae

[    0.909125]  [<ffffffff81012baa>] ? child_rip+0xa/0x20

[    0.909131]  [<ffffffff81011d61>] ? int_ret_from_sys_call+0x7/0x1b

[    0.909136]  [<ffffffff8101251d>] ? retint_restore_args+0x5/0x6

[    0.909142]  [<ffffffff81012ba0>] ? child_rip+0x0/0x20

I am using the Hypervisor 4.1.2 build from source.

The Dom0 ist running and there are no errors.

What does this message mean, and how can I solve this issue in order to startup my DomU's properly.

Thanks.

Cheers,

Maik

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users