Re: [BUG] kvm: guest can not startup due to triple fault

From: Dave Young
Date: Mon Oct 18 2010 - 00:43:52 EST


On Sun, Oct 17, 2010 at 8:15 PM, Avi Kivity <avi@xxxxxxxxxx> wrote:
> ÂOn 10/17/2010 12:14 PM, Dave Young wrote:
>>
>> On Sun, Oct 17, 2010 at 5:34 PM, Avi Kivity<avi@xxxxxxxxxx> Âwrote:
>> > Â ÂOn 10/17/2010 10:54 AM, Dave Young wrote:
>> >>
>> >> Âlinux guest can not startup normally, qemu keep rebooting.
>> >>
>> >> Âhost& Â Âguest both use linux-2.6.36-rc8+ kernel
>> >>
>> >> ÂAdd a dump_stack in x86.c around EXIT_SHUTDOWN code, I got:
>> >> Â[ 3924.503041] Pid: 1685, comm: qemu-system-x86 Not tainted
>> >> 2.6.36-rc8+
>> >> Â#62
>> >> Â[ 3924.503045] Call Trace:
>> >> Â[ 3924.503055] Â[<ffffffffa0176047>] handle_triple_fault+0x11/0x26
>> >> Â[kvm_intel]
>> >> Â[ 3924.503060] Â[<ffffffffa01772d2>] vmx_handle_exit+0x3df/0x474
>> >> Â[kvm_intel]
>> >> Â[ 3924.503080] Â[<ffffffffa021f203>]
>> >> kvm_arch_vcpu_ioctl_run+0x95f/0xc43
>> >> Â[kvm]
>> >> Â[ 3924.503087] Â[<ffffffff81503e54>] ?
>> >> __mutex_unlock_slowpath+0x11c/0x131
>> >> Â[ 3924.503101] Â[<ffffffffa021e1f9>] ? kvm_arch_vcpu_load+0x90/0xe6
>> >> [kvm]
>> >> Â[ 3924.503112] Â[<ffffffffa0210faf>] kvm_vcpu_ioctl+0x109/0x54a [kvm]
>> >> Â[ 3924.503117] Â[<ffffffff810bee76>] ?
>> >> Âfire_user_return_notifiers+0x2c/0x36
>> >> Â[ 3924.503122] Â[<ffffffff8106be93>] ? trace_hardirqs_on+0xd/0xf
>> >> Â[ 3924.503127] Â[<ffffffff81002789>] ? do_notify_resume+0x717/0x73d
>> >> Â[ 3924.503131] Â[<ffffffff8103994e>] ? finish_task_switch+0x69/0xda
>> >> Â[ 3924.503135] Â[<ffffffff8110628c>] do_vfs_ioctl+0x4c3/0x50d
>> >> Â[ 3924.503139] Â[<ffffffff8110632b>] sys_ioctl+0x55/0x77
>> >> Â[ 3924.503142] Â[<ffffffff81002c02>] system_call_fastpath+0x16/0x1b
>> >>
>> >> ÂAnyone can help on this?
>> >
>> > ÂPlease provide a trace (trace-cmd record -e kvm) leading to the
>> > failure.
>> >
>>
>> Hi, please see:
>> http://userweb.kernel.org/~davey/tmp/trace.dat
>>
>
> Was this done with an old version of trace-cmd? ÂPlease use the latest git.
> ÂMake sure you have udis86 and udis86-devel installed when you build it.

Hi, the trace-cmd was build from git version, but without udis86.

I updated trace.dat on the same url, is it a correct one?

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



--
Regards
dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/