From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754587Ab0JRI64 (ORCPT ); Mon, 18 Oct 2010 04:58:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:64705 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752925Ab0JRI6y (ORCPT ); Mon, 18 Oct 2010 04:58:54 -0400 Message-ID: <4CBC0C43.9060302@redhat.com> Date: Mon, 18 Oct 2010 10:58:43 +0200 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.4 MIME-Version: 1.0 To: Jan Kiszka , Steven Rostedt CC: Dave Young , kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [BUG] kvm: guest can not startup due to triple fault References: <20101017085416.GA1758@darkstar> <4CBAC342.1010609@redhat.com> <4CBAE8E2.1060704@redhat.com> <4CBBF3C8.9070104@web.de> <4CBC0B8C.7030003@redhat.com> In-Reply-To: <4CBC0B8C.7030003@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/18/2010 10:55 AM, Avi Kivity wrote: > On 10/18/2010 09:14 AM, Jan Kiszka wrote: >> Am 18.10.2010 06:43, Dave Young wrote: >> > On Sun, Oct 17, 2010 at 8:15 PM, Avi Kivity wrote: >> >> On 10/17/2010 12:14 PM, Dave Young wrote: >> >>> >> >>> On Sun, Oct 17, 2010 at 5:34 PM, Avi Kivity >> 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] [] >> handle_triple_fault+0x11/0x26 >> >>>>> [kvm_intel] >> >>>>> [ 3924.503060] [] vmx_handle_exit+0x3df/0x474 >> >>>>> [kvm_intel] >> >>>>> [ 3924.503080] [] >> >>>>> kvm_arch_vcpu_ioctl_run+0x95f/0xc43 >> >>>>> [kvm] >> >>>>> [ 3924.503087] [] ? >> >>>>> __mutex_unlock_slowpath+0x11c/0x131 >> >>>>> [ 3924.503101] [] ? >> kvm_arch_vcpu_load+0x90/0xe6 >> >>>>> [kvm] >> >>>>> [ 3924.503112] [] >> kvm_vcpu_ioctl+0x109/0x54a [kvm] >> >>>>> [ 3924.503117] [] ? >> >>>>> fire_user_return_notifiers+0x2c/0x36 >> >>>>> [ 3924.503122] [] ? trace_hardirqs_on+0xd/0xf >> >>>>> [ 3924.503127] [] ? >> do_notify_resume+0x717/0x73d >> >>>>> [ 3924.503131] [] ? >> finish_task_switch+0x69/0xda >> >>>>> [ 3924.503135] [] do_vfs_ioctl+0x4c3/0x50d >> >>>>> [ 3924.503139] [] sys_ioctl+0x55/0x77 >> >>>>> [ 3924.503142] [] >> 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? >> > >> >> IIUC, plugin_kvm is only involved in reporting, not recording, so udis86 >> shouldn't matter. >> >> I had a look out of curiosity (just managed to make my trace tools work >> smoothly), and the data is properly parsed by kernelshark here. There is >> a strange NMI storm going on right before the triple fault (on some MSR >> write) hits the fan. > > Doesn't parse here. I get a bus error. > > Steven, is trace.dat meant to be transportable? What does it depend on? > > Jan, can you upload your parsed data somewhere? I want to have a look > as well. > Never mind, user error here. -- error compiling committee.c: too many arguments to function