On Wed, Jan 05, 2011, Avi Kivity wrote about "Re: [Qemu-devel] [PATCH] Add VMX
cpuid feature to qemu64":
> IMO the emphasis on defaults is misplaced. Most people run virtual
> machines via a management tool, and we should focus on making it easy
> for management tool maintainers to do the right thing, by documenting
> our APIs and recommendations in the QEMU Management Tool Writer Guide.
Thanks. I'm withdrawing my patch, then, and will just keep the instruction
to use "-cpu host" in Nested VMX's README.
Just to add my last two cents on the subject, I think that from the same
assumption you make ("management tool maintainers will do the right thing")
I can draw an opposite conclusion: If qemu changes to use "kvm64" or "host"
by default, the management tool maintainers will any do the right thing by
explicitly stating the CPU type and not rely on the default, so nothing will
break. At the same time, people who do use the command line will benefit,
because they won't be baffled why the nested VMX feature, even if supported
by the KVM module, is hidden from them, while nested SVM isn't.
Thanks,
Nadav.
--
Nadav Har'El | Wednesday, Jan 5 2011, 29 Tevet 5771
n...@math.technion.ac.il |-----------------------------------------
Phone +972-523-790466, ICQ 13349191 |Seen on a sign outside a church: "This is
http://nadav.harel.org.il |a C H _ _ C H ... what's missing?"
