kvm-33 crash

kvm-33 crash

[Jun Koi]

Hi,

kvm-33 crashes on my Linux box. It happens after booting for few
seconds, ie not reached the prompt yet. And that never happens before
with previous versions on the same qemu image.

I want to post the boot log here, but dont know how to configure qemu
to do that. Any pointer?

Thanks,
Jun

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: kvm-33 crash

[Avi Kivity]

Jun Koi wrote:
> Hi,
>
> kvm-33 crashes on my Linux box. It happens after booting for few
> seconds, ie not reached the prompt yet. And that never happens before
> with previous versions on the same qemu image.
>
> I want to post the boot log here, but dont know how to configure qemu
> to do that. Any pointer?
>
>   

What crashes?  The guest or the host?  What kernel versions?


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: kvm-33 crash

[Jun Koi]

On 7/26/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> Jun Koi wrote:
> > Hi,
> >
> > kvm-33 crashes on my Linux box. It happens after booting for few
> > seconds, ie not reached the prompt yet. And that never happens before
> > with previous versions on the same qemu image.
> >
> > I want to post the boot log here, but dont know how to configure qemu
> > to do that. Any pointer?
> >
> >
>
> What crashes?  The guest or the host?  What kernel versions?
>
>

The guest crashed. Host kernel is 2.6.21, and same for guest.

Thanks,
Jun

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: kvm-33 crash

[Jun Koi]

On 7/26/07, Jun Koi <junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On 7/26/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> > Jun Koi wrote:
> > > Hi,
> > >
> > > kvm-33 crashes on my Linux box. It happens after booting for few
> > > seconds, ie not reached the prompt yet. And that never happens before
> > > with previous versions on the same qemu image.
> > >
> > > I want to post the boot log here, but dont know how to configure qemu
> > > to do that. Any pointer?
> > >
> > >
> >
> > What crashes?  The guest or the host?  What kernel versions?
> >
> >
>
> The guest crashed. Host kernel is 2.6.21, and same for guest.
>

I figure it out why it crashes: my guest (Linux 2.6.21) is compiled
with SMP kernel. If I run qemu without -smp option, it crashes. But
with -smp option, it is fine.

So this is a bug, and should be fixed.

Thanks,
Jun

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: kvm-33 crash

[Avi Kivity]

Jun Koi wrote:
> On 7/26/07, Jun Koi <junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>   
>> On 7/26/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>>     
>>> Jun Koi wrote:
>>>       
>>>> Hi,
>>>>
>>>> kvm-33 crashes on my Linux box. It happens after booting for few
>>>> seconds, ie not reached the prompt yet. And that never happens before
>>>> with previous versions on the same qemu image.
>>>>
>>>> I want to post the boot log here, but dont know how to configure qemu
>>>> to do that. Any pointer?
>>>>
>>>>
>>>>         
>>> What crashes?  The guest or the host?  What kernel versions?
>>>
>>>
>>>       
>> The guest crashed. Host kernel is 2.6.21, and same for guest.
>>
>>     
>
> I figure it out why it crashes: my guest (Linux 2.6.21) is compiled
> with SMP kernel. If I run qemu without -smp option, it crashes. But
> with -smp option, it is fine.
>
> So this is a bug, and should be fixed.
>
>   

Yes.  I updated http://kvm.qumranet.com/kvmwiki/Bugs to include 
information on extracting a serial log.  Also, please post your .config 
along with the guest log.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: kvm-33 crash

[Jun Koi]

[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]

On 7/26/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> Jun Koi wrote:
> > On 7/26/07, Jun Koi <junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> >> On 7/26/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> >>
> >>> Jun Koi wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> kvm-33 crashes on my Linux box. It happens after booting for few
> >>>> seconds, ie not reached the prompt yet. And that never happens before
> >>>> with previous versions on the same qemu image.
> >>>>
> >>>> I want to post the boot log here, but dont know how to configure qemu
> >>>> to do that. Any pointer?
> >>>>
> >>>>
> >>>>
> >>> What crashes?  The guest or the host?  What kernel versions?
> >>>
> >>>
> >>>
> >> The guest crashed. Host kernel is 2.6.21, and same for guest.
> >>
> >>
> >
> > I figure it out why it crashes: my guest (Linux 2.6.21) is compiled
> > with SMP kernel. If I run qemu without -smp option, it crashes. But
> > with -smp option, it is fine.
> >
> > So this is a bug, and should be fixed.
> >
> >
>
> Yes.  I updated http://kvm.qumranet.com/kvmwiki/Bugs to include
> information on extracting a serial log.  Also, please post your .config
> along with the guest log.
>

Here comes the boot log serial.txt.

Let me know if you need anything else.

Thanks,
Jun.

[-- Attachment #2: serial.txt --]
[-- Type: text/plain, Size: 4446 bytes --]

Linux version 2.6.21.1 (root@zoo) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #4 SMP Wed Jul 25 13:06:41 KST 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000e8000 size: 0000000000018000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 0000000018ef0000 end: 0000000018ff0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 0000000018ff0000 size: 0000000000010000 end: 0000000019000000 type: 3
copy_e820_map() start: 00000000fffc0000 size: 0000000000040000 end: 0000000100000000 type: 2
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000018ff0000 (usable)
 BIOS-e820: 0000000018ff0000 - 0000000019000000 (ACPI data)
 BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
399MB LOWMEM available.
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->   102384
early_node_map[1] active PFN ranges
    0:        0 ->   102384
DMI not present or invalid.
Allocating PCI resources starting at 20000000 (gap: 19000000:e6fc0000)
Built 1 zonelists.  Total pages: 101585
Kernel command line: root=/dev/hda1 ro console=ttyS0,115200
Found and enabled local APIC!
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Detected 1995.021 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 402844k/409536k available (1627k kernel code, 6172k reserved, 533k data, 160k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xfffbc000 - 0xfffff000   ( 268 kB)
    vmalloc : 0xd9800000 - 0xfffba000   ( 615 MB)
    lowmem  : 0xc0000000 - 0xd8ff0000   ( 399 MB)
      .init : 0xc0323000 - 0xc034b000   ( 160 kB)
      .data : 0xc0296ff1 - 0xc031c5b4   ( 533 kB)
      .text : 0xc0100000 - 0xc0296ff1   (1627 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4112.83 BogoMIPS (lpj=8225662)
Mount-cache hash table entries: 512
CPU: L1 I cache: 8K
CPU: L2 cache: 128K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 11k freed
CPU0: Intel QEMU Virtual CPU version 0.9.0 stepping 03
SMP motherboard not detected.
general protection fault: 0000 [#1]
SMP 
Modules linked in:
CPU:    0
EIP:    0060:[<c0112ac2>]    Not tainted VLI
EFLAGS: 00000246   (2.6.21.1 #4)
EIP is at setup_apic_nmi_watchdog+0x372/0x440
eax: 00000000   ebx: 00000000   ecx: 000000c1   edx: 00000000
esi: c0348180   edi: c0348180   ebp: c1323e80   esp: c13a1e6c
ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Process swapper (pid: 1, ti=c13a0000 task=d8fc4a30 task.ti=c13a0000)
Stack: 00000000 c032a7b5 00000001 c13a1ed8 c0350000 00000000 c032ae56 00000021 
       00000000 00000000 00000000 00000001 00000000 00000000 00000000 00000000 
       00000000 00000000 00000000 00000001 00000000 00000000 00000000 00000000 
Call Trace:
 [<c032a7b5>] verify_local_APIC+0x85/0x150
 [<c032ae56>] APIC_init_uniprocessor+0x76/0x110
 [<c032981c>] smp_prepare_cpus+0x1ec/0x670
 [<c0118279>] task_rq_lock+0x39/0x70
 [<c011a988>] set_cpus_allowed+0x48/0xa0
 [<c03234a0>] init+0x0/0x280
 [<c03234db>] init+0x3b/0x280
 [<c0102c8e>] ret_from_fork+0x6/0x1c
 [<c03234a0>] init+0x0/0x280
 [<c03234a0>] init+0x0/0x280
 [<c010395f>] kernel_thread_helper+0x7/0x18
 =======================
Code: e8 64 f8 ff ff 85 c0 0f 84 e2 fc ff ff ba 86 01 00 00 b8 ff ff ff ff e8 7d f6 ff ff 85 c0 74 77 31 db b9 c1 00 00 00 89 d8 89 da <0f> 30 be 86 01 00 00 b8 79 00 13 00 89 f1 0f 30 a1 8c b6 2f c0 
EIP: [<c0112ac2>] setup_apic_nmi_watchdog+0x372/0x440 SS:ESP 0068:c13a1e6c
Kernel panic - not syncing: Attempted to kill init!

[-- Attachment #3: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #4: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-33 crash

[Avi Kivity]

Jun Koi wrote:
>>>
>>> I figure it out why it crashes: my guest (Linux 2.6.21) is compiled
>>> with SMP kernel. If I run qemu without -smp option, it crashes. But
>>> with -smp option, it is fine.
>>>
>>> So this is a bug, and should be fixed.
>>>
>>>
>>>       
>> Yes.  I updated http://kvm.qumranet.com/kvmwiki/Bugs to include
>> information on extracting a serial log.  Also, please post your .config
>> along with the guest log.
>>
>>     
>
> Here comes the boot log serial.txt.
>   

It's the nmi watchdog.  Unfortunately emulating that msr will be a 
pain.  You can workaround disabling it in .config by booting with 
nmi_watchdog=0 (?).  Note that 2.6.23 checks the msr and won't fail.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/