On Mon, Oct 18, 2010 at 10:19 PM, Avi Kivity <avi@xxxxxxxxxx> wrote: > Â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. > Yes, there's no nx in guest cpuinfo hardware_setup is run only when insmod so the nx is of host, thus the first printk result is right value? > -- > error compiling committee.c: too many arguments to function > > -- Regards dave -- 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
