On 15.06.2009, at 14:17, Christoph Hellwig wrote:
On Mon, Jun 15, 2009 at 01:30:05PM +0200, Alexander Graf wrote:
X86 CPUs need to have some magic happening to enable the
virtualization
extensions on them. This magic can result in unpleasant results for
users, like blocking other VMMs from working (vmx) or using invalid
TLB
entries (svm).
Currently KVM activates virtualization when the respective kernel
module
is loaded. This blocks us from autoloading KVM modules without
breaking
other VMMs.
That will only become interesting if we every have such a thing in
mainline. So NACK, lots of complication for no good reason.
I don't want to fight political battles here. Seriously - we're out of
kindergarden.
There are users out there who want to have VBox/VMware and kvm
installed in parallel and can't have both kernel modules loaded at the
same time. We're only hurting _our_ users, not the others if we keep
people from having kvm*.ko loaded.
Sigh.
Alex
--
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
