From: Eli Collins <ecollins@vmware.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: "devzero@web.de" <devzero@web.de>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Javier Guerra <javier@guerrag.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: Linux with kvm-intel locks up VMplayer guest is started
Date: Wed, 18 Jun 2008 18:08:56 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0806181552130.14608@ecollins-dev1.eng.vmware.com> (raw)
In-Reply-To: <48596780.7080004@codemonkey.ws>
Hi Martin,
This lockup is fixed in the latest dot releases of Workstation, Player,
and Server.
The vmmon module now checks if VT is already enabled (actually it just
tests if CR4.VMXE is set since checking if the cpu is in VMX mode is a
pain). The vmmon module enables VMX mode when world switching to our
monitor and disables it when world switching back to the host. The
kvm-intel module puts the cpu(s) in VMX mode and does not exit VMX mode
until the module is unloaded, so if you want to run player and kvm you
need to first unload the kvm-intel module. However, this only works with
very recent kvm modules. If you're using a kvm-intel module that doesn't
contain the patch I submitted a couple weeks ago then even unloading the
kvm-intel module is not enough since it leaves CR4.VMXE set. So for "old"
modules you need to not load the kvm-intel module in the first place.
Note that the above is only relevant to kvm-intel. The vmmon and kvm-amd
modules do not need exclusive access to SVM mode. I've run VMs on kvm-69
and Workstation 6.5 beta simultaneously on an AMD-V host without any
issues.
Also note that this issue is relevant for any software that wants to use
VT: QEMU, VirtualBox, Parallels, etc. won't be able to if the host (via
the kvm-intel module) has already claimed it.
Thanks,
Eli
next prev parent reply other threads:[~2008-06-19 1:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 19:05 devzero
2008-06-18 19:52 ` Anthony Liguori
2008-06-19 1:08 ` Eli Collins [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-16 15:05 Martin Michlmayr
2008-06-16 15:21 ` Anthony Liguori
2008-06-17 12:39 ` Martin Michlmayr
2008-06-17 13:16 ` Anthony Liguori
2008-06-17 13:32 ` Martin Michlmayr
2008-06-17 13:44 ` Martin Michlmayr
2008-06-17 14:02 ` Javier Guerra
2008-06-17 15:29 ` Alan Cox
2008-06-17 18:09 ` Anthony Liguori
2008-06-18 13:56 ` Avi Kivity
2008-06-18 20:59 ` Anthony Liguori
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=alpine.DEB.1.10.0806181552130.14608@ecollins-dev1.eng.vmware.com \
--to=ecollins@vmware.com \
--cc=anthony@codemonkey.ws \
--cc=devzero@web.de \
--cc=javier@guerrag.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tbm@cyrius.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
all inboxes | Powered by JetHome®