Re: KVM guest crashes

[Alexander Graf <agraf@suse.de>]

Avi Kivity wrote:
> Alexander Graf wrote:
>> The guest kernels included here are openSUSE 11.0 (2.6.25) and 11.1
>> (2.6.27) kernels.
>>
>> Find the tests here: http://alex.csgraf.de/kvm-tests.tar.bz2
>> And some logs here (NPT enabled): http://alex.csgraf.de/kvm-logs.tar.bz2
>>
>> I'm somewhat lost on the reason for these failures, so if you do have
>> some time on your hands, please give me a hand debugging this! If I'd
>> had to guess, I'd say it's either an APIC issue and/or guest memory
>> corruption.
>>   
>
> I'd guess memory corruption.
>
> Does running a uniprocessor guest help?  What about a uniprocessor
> guest pinned to one host core?

So last night I started several guests with -smp 8 but without network
to see if IO load is causing the problems. All VMs are down, but one
panic log is rather new:

Stuck ??
Stuck ??
Stuck ??
Stuck ??
Stuck ??
Stuck ??
BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
IP: [<ffffffff80237454>] cpu_attach_domain+0x84/0x207
PGD 0
Oops: 0000 [1] SMP
last sysfs file:
CPU 1
Modules linked in:
Supported: Yes
Pid: 1, comm: swapper Tainted: G S        2.6.27.11-1-default #1
RIP: 0010:[<ffffffff80237454>]  [<ffffffff80237454>]
cpu_attach_domain+0x84/0x207
RSP: 0018:ffff88007a419c50  EFLAGS: 00010202
RAX: 0000000000000000 RBX: ffff880001077a60 RCX: ffff88007a419c40
RDX: 000000000000044d RSI: 0000000000000200 RDI: 0000000000000000
RBP: ffff88007a419c90 R08: 0000000000000000 R09: 0000000000000200
R10: 0000000000000008 R11: 0000000000018600 R12: ffff8800010778d0
R13: ffff880001077a78 R14: ffff8800010775b0 R15: ffff88000107f700
FS:  0000000000000000(0000) GS:ffff88007afeb540(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process swapper (pid: 1, threadinfo ffff88007a418000, task ffff88007a406040)
Stack:  000000047a4616c0 ffff88007a548000 0000002f0000044d 0000000000000004
 ffffffff80a275b0 0000000000000000 ffff88007a460e00 ffff88007a45c140
 ffff88007a419ec0 ffffffff80238190 ffff88007a419dc0 ffff88007a419e00
Call Trace:
 [<ffffffff80238190>] __build_sched_domains+0xbb9/0xbf5
 [<ffffffff80981ae4>] sched_init_smp+0xa9/0x1d8
 [<ffffffff8096b850>] kernel_init+0x74/0xea
 [<ffffffff8020cf79>] child_rip+0xa/0x11


Code: 00 4c 89 ef 89 45 d4 8b 83 88 00 00 00 89 45 d0 e8 d1 05 13 00 ff
c8 74 5d 8b 93 88 00 00 00 f7 c2 8f 02 00 00 74 0d 48 8b 43 10 <48> 3b
00 0f 85 24 01 00 00 80 e2 70 0f 85 1b 01 00 00 eb 37 48
RIP  [<ffffffff80237454>] cpu_attach_domain+0x84/0x207
 RSP <ffff88007a419c50>
CR2: 0000000000000000
---[ end trace 4eaa2a86a8e2da22 ]---
Kernel panic - not syncing: Attempted to kill init!


>From what I've seen it's always related to IPIs, but that's just a
guess. I'll start UP testing now.

Alex