From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [BUG] kvm: guest can not startup due to triple fault Date: Tue, 19 Oct 2010 17:04:46 +0200 Message-ID: <4CBDB38E.7090801@redhat.com> References: <4CBAE8E2.1060704@redhat.com> <4CBBF3C8.9070104@web.de> <4CBC1047.6010501@redhat.com> <20101018125803.GA2497@darkstar> <4CBC4B06.3030300@redhat.com> <20101018134508.GA11885@darkstar> <4CBC4FA9.90406@redhat.com> <4CBC5097.1020105@redhat.com> <20101018135813.GA20316@darkstar> <4CBC547A.8080700@redhat.com> <4CBC964B.6000605@zytor.com> <4CBD099D.2060500@zytor.com> <4CBD5D8F.6020505@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Dave Young , Ingo Molnar , Jan Kiszka , kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: "H. Peter Anvin" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 10/19/2010 04:56 PM, H. Peter Anvin wrote: > Right... note in particular that the BIOS sets them up inconsistently. The kernel is doing the rufht thing: since NX isn't available on all processors it is considered unavailable. I guess kvm should be modified to mask GET_SUPPORTED_CPUID results with the boot_cpu features. This will make kvm take advantage of the core kernel doing the right thing.