Re: kvm-45 problems

Zhao, Yunfeng
2007-10-10T02:47:20Z

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

This fix cannot resolve this issue.
Against latest kvm commits, SMP linux with 4 vcpus still cannot boot up.
But the issue will not happen , if adding "-smp4 -no-acpi".

Here is the error info in dmesg
BUG: soft lockup detected on CPU#0!
[<c044a0b7>] softlockup_tick+0x98/0xa6
[<c042cc98>] update_process_times+0x39/0x5c
[<c04176ec>] smp_apic_timer_interrupt+0x5c/0x64
[<c04049bf>] apic_timer_interrupt+0x1f/0x24
[<f8abdfb7>] kvm_flush_remote_tlbs+0xcc/0xdb [kvm]
[<f8ac3467>] kvm_mmu_pte_write+0x1f2/0x368 [kvm]
[<f8abe7bb>] emulator_write_emulated_onepage+0x73/0xe6 [kvm]
[<f8ac6268>] x86_emulate_insn+0x20c2/0x3122 [kvm]
[<f8ac3f86>] x86_decode_insn+0x624/0x844 [kvm]
[<f8abebd6>] emulate_instruction+0x12b/0x258 [kvm]
[<f8a172d0>] handle_exception+0x163/0x23f [kvm_intel]
[<f8a17087>] kvm_handle_exit+0x70/0x8a [kvm_intel]
[<f8abf1fd>] kvm_vcpu_ioctl_run+0x21a/0x31f [kvm]
[<f8abf3fc>] kvm_vcpu_ioctl+0x0/0xc58 [kvm]
[<f8abf4ff>] kvm_vcpu_ioctl+0x103/0xc58 [kvm]
[<c04db744>] __next_cpu+0x12/0x21
[<c041c97f>] find_busiest_group+0x177/0x462
[<c041d3cd>] enqueue_task+0x29/0x39
[<c041d3f9>] __activate_task+0x1c/0x29
[<c041dc43>] try_to_wake_up+0x371/0x37b
[<c05facb9>] schedule+0x90d/0x9ba
[<c041c41c>] __wake_up_common+0x2f/0x53
[<c041d20d>] __wake_up+0x2a/0x3d
[<c0437cef>] wake_futex+0x3a/0x44
[<c0437fbf>] futex_wake+0xa9/0xb3
[<c0438b9e>] do_futex+0x20d/0xb15
[<c04db744>] __next_cpu+0x12/0x21
[<c042d849>] __dequeue_signal+0x151/0x15c
[<c042e942>] dequeue_signal+0x2d/0x9c
[<c0415b61>] smp_call_function_interrupt+0x3e/0x52
[<f8abf3fc>] kvm_vcpu_ioctl+0x0/0xc58 [kvm]
[<c040499b>] call_function_interrupt+0x1f/0x24
[<f8abf3fc>] kvm_vcpu_ioctl+0x0/0xc58 [kvm]
[<c0415b61>] smp_call_function_interrupt+0x3e/0x52
[<f8abf3fc>] kvm_vcpu_ioctl+0x0/0xc58 [kvm]
[<c0479cc8>] do_ioctl+0x1c/0x5d
[<c0479f53>] vfs_ioctl+0x24a/0x25c
[<c0479fad>] sys_ioctl+0x48/0x5f
[<c0403eff>] syscall_call+0x7/0xb

>-----Original Message-----
>From: Avi Kivity [mailto:avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org]
>Sent: 2007年10月9日 18:19
>To: Zhao, Yunfeng
>Cc: kvm-devel
>Subject: Re: [kvm-devel] kvm-45 problems
>
>Avi Kivity wrote:
>> Zhao, Yunfeng wrote:
>>
>>> We run some booting multiple guest tests in our nightly testing.
>>> Like booting two UP windows guests, booting one UP linux guest and one UP
>windows guest, and booting 4 UP linux guests.
>>> The first two cases have no problem in our testing.
>>> And booting 4 UP linux guests may crash host, but this problem doesn't happen
>very time. If the problem didn't happen, linux guest can be log in without any
>problem.
>>>
>>> For smp guest, we meet a problem that booting linux guest with 4 vcpus causes
>soft lock error on host. Once this error happened, qemu process also could not
>be killed.
>>>
>>> Our linux guests are using 2.6.9, 2.6.16, and 2.6.23 kernels.
>>>
>>>
>>>
>>
>> This may be due to NMIs or MCEs. Is it possible your machine is
>> receiving them?
>>
>
>
>I pushed a fix for the NMI issue. Can you check if it fixes your hangs?
>
>
>--
>error compiling committee.c: too many arguments to function