From: Alexander Graf <agraf@suse.de>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com, kraxel@redhat.com,
anthony@codemonkey.ws, Sander.Vanleeuwen@sun.com,
zach@vmware.com, brogers@novell.com
Subject: Re: [PATCH] Activate Virtualization On Demand v2
Date: Wed, 05 Nov 2008 12:01:04 +0100 [thread overview]
Message-ID: <49117CF0.6000400@suse.de> (raw)
In-Reply-To: <20081105105812.GC25523@redhat.com>
Daniel P. Berrange wrote:
> On Wed, Nov 05, 2008 at 09:48:16AM +0100, 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.
>>
>> To circumvent this problem at least a bit, this patch introduces on
>> demand activation of virtualization. This means, that instead
>> virtualization is enabled on creation of the first virtual machine
>> and disabled on removal of the last one.
>>
>
> Pardon my unfamiliarity with the code, but with this change applied,
> will we still get an explicit error at time of loading kvm-intel.ko
> if VMX were disabled in the BIOS ? Or will that error reporting be
> pushed off to time when VMX is first activated ?
>
The BIOS and hardware support checks are in kvm_arch_init, which is
still called at load-time of the module.
Alex
next prev parent reply other threads:[~2008-11-05 11:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 8:48 [PATCH] Activate Virtualization On Demand v2 Alexander Graf
2008-11-05 10:06 ` Avi Kivity
2008-11-05 10:28 ` Alexander Graf
2008-11-05 10:45 ` Avi Kivity
2008-11-05 10:53 ` Alexander Graf
2008-11-05 11:23 ` Alexander Graf
2008-11-05 10:45 ` Zhang, Xiantao
2008-11-05 10:54 ` Alexander Graf
2008-11-05 10:58 ` Daniel P. Berrange
2008-11-05 11:01 ` Alexander Graf [this message]
2008-11-05 13:06 ` Christian Borntraeger
2008-11-05 13:12 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 11:30 Alexander Graf
2009-06-15 12:17 ` Christoph Hellwig
2009-06-15 12:25 ` Alexander Graf
2009-06-15 12:27 ` Christoph Hellwig
2009-06-16 14:02 ` Avi Kivity
2009-06-16 14:01 ` Avi Kivity
2009-06-16 14:08 ` Alexander Graf
2009-06-16 15:13 ` Avi Kivity
2009-06-17 21:56 ` Alexander Graf
2009-06-18 8:35 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49117CF0.6000400@suse.de \
--to=agraf@suse.de \
--cc=Sander.Vanleeuwen@sun.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=brogers@novell.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=zach@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox