From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753522Ab0JQMPg (ORCPT ); Sun, 17 Oct 2010 08:15:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:4357 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751893Ab0JQMPf (ORCPT ); Sun, 17 Oct 2010 08:15:35 -0400 Message-ID: <4CBAE8E2.1060704@redhat.com> Date: Sun, 17 Oct 2010 14:15:30 +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: Dave Young CC: 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> In-Reply-To: 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/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. -- error compiling committee.c: too many arguments to function