On 10/18/2010 04:25 PM, Dave Young wrote:
> > 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?
There's no right value since the two cpus have different values for nx. -- 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
