From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Young Subject: Re: [BUG] kvm: guest can not startup due to triple fault Date: Mon, 18 Oct 2010 21:45:08 +0800 Message-ID: <20101018134508.GA11885@darkstar> References: <20101017085416.GA1758@darkstar> <4CBAC342.1010609@redhat.com> <4CBAE8E2.1060704@redhat.com> <4CBBF3C8.9070104@web.de> <4CBC1047.6010501@redhat.com> <20101018125803.GA2497@darkstar> <4CBC4B06.3030300@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jan Kiszka , kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: Avi Kivity Return-path: Content-Disposition: inline In-Reply-To: <4CBC4B06.3030300@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Mon, Oct 18, 2010 at 03:26:30PM +0200, Avi Kivity wrote: > On 10/18/2010 02:58 PM, Dave Young wrote: > >> > >> It's secondary_startup_64 enabling efer.sce and efer.nx. > >> > >> Dave, please post your /proc/cpuinfo. Is your host running with NX > >> disabled? > > > >I see nx bit in /proc/cpuinfo, Actually I don't know how to disable it. > > Strange. > > Please patch arch/x86/kvm/x86.c to printk efer_reserved_bits (a > global), efer (an argument) and old_efer (a local), and post the > results. I add printk before kvm_mmu_reset_context(vcpu), correct? get following value: [ 3228.468325] efer_reserved_bits = 0xfffffffffffffafe [ 3228.468328] efer = 0x100 [ 3228.468330] old_efer = 0x0