On Mon, May 30, 2011, Jan Kiszka wrote about "Re: drop -enable-nesting": > > "-enable-nesting" could remain as a synonym for enabling either VMX or SVM > > in the guest, depending on what was available in the host (because KVM now > > supports both nested SVM and nested VMX, but not SVM-on-VMX or vice versa). > > Why? Once nesting is stable (I think SVM already is), there is no reason > for an explicit enable. And you can always mask it out via -cpu. As far as I understand (and this was previously discussed on the QEMU mailing list), the default emulated CPU does not include the "vmx" capability, and you need to enable it with something like "-cpu qemu64,+vmx" (or "-cpu host"). I am not sure if it does enable the "svm" capability. If it does, it isn't useful when KVM is enabled and the underlying host has VMX, not SVM. Nadav. -- Nadav Har'El | Monday, May 30 2011, 27 Iyyar 5771 nyh@xxxxxxxxxxxxxxxxxxx |----------------------------------------- Phone +972-523-790466, ICQ 13349191 |Why do we drive on a parkway and park on http://nadav.harel.org.il |a driveway? -- 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
