From: Muli Ben-Yehuda <mulix@mulix.org>
To: Jun Koi <junkoi2004@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Nested KVM is weird?
Date: Sun, 1 Jun 2014 13:59:27 +0300 [thread overview]
Message-ID: <20140601105927.GD2385@needle> (raw)
In-Reply-To: <CA+g7VZ3kFEGjeiQLnoK4GFAYU4=Y-4HU1gzz15A-sCO406qekQ@mail.gmail.com>
On Sun, Jun 01, 2014 at 05:54:25PM +0700, Jun Koi wrote:
> So this means ESXi never uses VMResume/VMLaunch? How is this
> possible, because it uses VMX for its implementation?
ESXi will fall back to binary translation if it decides that it cannot
use VMX for some reason. Look at the L2's log file inside ESXi and you
will likely find some errors related to running nested, MSRs KVM does
not emulate properly, or something else that causes ESXi to use binary
translation for its L2.
Cheers,
Muli
next prev parent reply other threads:[~2014-06-01 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 10:54 [Qemu-devel] Nested KVM is weird? Jun Koi
2014-06-01 10:59 ` Muli Ben-Yehuda [this message]
2014-06-01 16:30 ` Jun Koi
2014-06-03 10:53 ` Muli Ben-Yehuda
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=20140601105927.GD2385@needle \
--to=mulix@mulix.org \
--cc=junkoi2004@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).