On 08/01/2012 05:26 PM, Stefan Bader wrote: >>> According to Intel SDM there was never CPU that didn't support RDPMC >>> exiting. Looks like unfortunate nested VMX bug. >> >> Moreover, that same commit fixes the bug in nested vmx. So if you >> update your host kernel to the same version as your L1 guest (or, at >> your option, any later version) it should work. >> >> We could backport that part of the patch, though as nested vmx is still >> experimential, I don't think it's worth it. >> > Though this is probably what people will (or will have to) do. The host is not > always under your control. Even with it being experimental, it was working (at > least the module was loadable) before and is now broken on Intel hosts. > But ok, so the recommendation is to rather backport support to the host kernel > than to try handling this differently in the guest module, right? Right - it's not just kvm-as-a-guest that will trip on this. But there's no point in everyone backporting it on their own. If you're doing the backport, please post it here and we'll forward it to the stable branch. -- 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
