Debian 6.0 XEN on DL585 // hard reset when starting a DomU (VM)

[jsc69]

Hello,

I have some strange behavior with a DL585 G7 with only two cpu sockets used. I use Debian 6.0 with a XEN Kernel. Every time, when I start a DomU the server makes a hard reset without any kernel panic or output.

When I start with the same disks in another DL585 G7 with all four cpu sockets used, everything works normal!

We use many Debian 6.0 Xen Server on diffrent HP Hardware - never seen before...

I found some difference in the dmesg output on the two servers:

on the non working DL585:

[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at 0000000000000000-0000000180000000
[    0.000000] Bootmem setup node 0 0000000000000000-0000000180000000
[    0.000000]   NODE_DATA [0000000000008000 - 000000000000ffff]
[    0.000000]   bootmap [0000000000010000 -  000000000003ffff] pages 30
[    0.000000] (9 early reservations) ==> bootmem [0000000000 - 0180000000]
[    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
[    0.000000]   #1 [00040de000 - 0004103000]   XEN PAGETABLES ==> [00040de000 - 0004103000]
[    0.000000]   #2 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
[    0.000000]   #3 [0001000000 - 00016e7b44]    TEXT DATA BSS ==> [0001000000 - 00016e7b44]
[    0.000000]   #4 [0001708000 - 00034dce00]          RAMDISK ==> [0001708000 - 00034dce00]
[    0.000000]   #5 [00034dd000 - 00040de000]   XEN START INFO ==> [00034dd000 - 00040de000]
[    0.000000]   #6 [00016e8000 - 00016e8180]              BRK ==> [00016e8000 - 00016e8180]
[    0.000000]   #7 [0000100000 - 00006cc000]          PGTABLE ==> [0000100000 - 00006cc000]
[    0.000000]   #8 [0004103000 - 0004505000]          PGTABLE ==> [0004103000 - 0004505000]

on the working:

[    0.000000] Scanning NUMA topology in Northbridge 24
[    0.000000] Number of nodes 8
[    0.000000] Node 0 MemBase 0000000000000000 Limit 000000013f600000
[    0.000000] Node 1 bogus settings 440000000-13f600000.
[    0.000000] Node 2 bogus settings 640000000-13f600000.
[    0.000000] Node 3 bogus settings 840000000-13f600000.
[    0.000000] Node 4 bogus settings a40000000-13f600000.
[    0.000000] Node 5 bogus settings c40000000-13f600000.
[    0.000000] Node 6 bogus settings e40000000-13f600000.
[    0.000000] Node 7 bogus settings 1040000000-13f600000.
[    0.000000] NUMA: Using 63 for the hash shift.
[    0.000000] Using node hash shift of 63

I also found some informations about the issue in the iLO log,

Please Help!