On 09/22/2010 12:49 PM, Nadav Har'El wrote:
On Tue, Sep 21, 2010, Chris Wright wrote about "Re: KVM call minutes for Sept 21":
People keep looking for reasons to justify the cost of the effort, dunno
why "because it's cool" isn't good enough ;) At any rate, that was mainly
a question of how it might be useful for production kind of environments.
I gave in my previous mail a long list of examples what you might do with
nested virtualization, and many of them could be called "production kind of
enviroments".
I don't think arguing about use cases is very productive.
The concern is that nested VMX is invasive and presents a long term
maintenance burden. There are two ways to mitigate this burden. The
first is to work extra hard to make things as common as humanly possible
between nested VMX and nested SVM. The second is to make sure that we
have an aggressive set of test cases.
I think the later is perhaps the most important point of all.
Regards.
Anthony Liguori
--
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
