On 10/18/2010 04:15 PM, Dave Young wrote:
On Mon, Oct 18, 2010 at 10:13 PM, Avi Kivity<avi@xxxxxxxxxx> wrote: > On 10/18/2010 04:11 PM, Dave Young wrote: >> >> On Mon, Oct 18, 2010 at 10:06 PM, Avi Kivity<avi@xxxxxxxxxx> wrote: >> > On 10/18/2010 03:58 PM, Dave Young wrote: >> >> >> >> > >> >> > Please patch hardware_setup() to show the value of >> >> > boot_cpu_has(X86_FEATURE_NX). >> >> >> >> It's 0 >> >> Please wait, I reply too quick, actually it boots two times fine then >> one time fail. > > What boots fine? The guest? Yes the guest
That makes some sort of wierd sense. First kvm samples X86_FEATURE_NX, sees that it has the feature, reports it to qemu, qemu runs the guest, NX gets disabled in between, the guest tries to enable NX, kvm kills it.
Second time round, kvm reports that NX is not available, qemu does not enable it, neither does the guest, and everyone is happy.
Please confirm that when the guest does boot, it boots without NX in /proc/cpuinfo.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
