Re: [PATCH] [RFC] Activate VMX on demand

[Avi Kivity <avi@redhat.com>]

Alexander Graf wrote:
> This patch moves the actual VMX enablement from the initialization
> of the module to the creation of a VCPU.
>
> With this approach, KVM can be easily autoloaded and does not block
> other VMMs while being modprobe'd.
> This improves the user experience a lot, since now other VMMs can
> run, even though KVM is loaded, so users do not have to manually
> load/unload KVM or any other VMM module.
>
> Compared to the previously suggested approach "2", which would
> introduce a complete framework that brings almost no benefit,
> this approach enables coexistence of multiple VMMs without much
> intervention. Thanks to Gerd for pointing that out.
>
> I verified that this approach works with VirtualBox.
>
>   

This should be done in x86.c and made to apply to svm as well.  Other 
VMMs would use efer.svme as an indication that svm is in use, similar to 
cr4.vmxe today.

I'm not thrilled about this (it could be done, much more simply, by 
having the other hypervisor rmmod kvm), but okay.

-- 
error compiling committee.c: too many arguments to function