Comment 60 for bug 218126

I have similar issues with a Centos 5.1 Dom0 and a Hardy DomU.

I am fine if I use the gutsy Xen kernel (2.6.22-14.46), but get the same kernel panic with the vanilla Hardy Xen kernel.

I've just tried the kernel from proposed and whilst the VM boots a lot quicker, I still get the following error

[ 0.420184] io scheduler cfq registered (default)
[ 0.423651] Xen virtual console successfully installed as tty1
[ 0.423856] Event-channel device installed.
[ 0.443551] Successfully initialized TPM backend driver.
[ 0.459780] netfront: Initialising virtual ethernet driver.
[ 0.461803] xen-vbd: registered block device major 8
[ 0.516216] ------------[ cut here ]------------
[ 0.516241] kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:855!
[ 0.516269] invalid opcode: 0000 [#1] SMP
[ 0.516304] Modules linked in:
[ 0.516323]
[ 0.516337] Pid: 18, comm: xenwatch Not tainted (2.6.24-17-xen #1)
[ 0.516350] EIP: 0061:[<c0269cc3>] EFLAGS: 00010002 CPU: 0
[ 0.516370] EIP is at network_alloc_rx_buffers+0x503/0x510
[ 0.516382] EAX: 00000040 EBX: c90219b4 ECX: 00000041 EDX: 0000003f
[ 0.516393] ESI: 00007644 EDI: c9020480 EBP: 0000023f ESP: c7ed1edc
[ 0.516407] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: e021
[ 0.516420] Process xenwatch (pid: 18, ti=c7ed0000 task=c7ecabd0 task.ti=c7ed0000)
[ 0.516431] Stack: ffffffff c902119c c9020000 000007e0 00000100 003f4500 00000040 00000000

The system is an Athlon XP 2000+ running the vanilla Centos 5.1 Xen install.