public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 3 Jun 2014 13:53:50 +0300	[thread overview]
Message-ID: <20140603105350.GA9296@needle> (raw)
In-Reply-To: <CA+g7VZ05M3NV11A1c4tsnAuBCdvdnirOk-==s2rP1MrrpU909g@mail.gmail.com>

On Sun, Jun 01, 2014 at 11:30:02PM +0700, Jun Koi wrote:

> (1) do you think this VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL is the
>     reason why ESXi falls back to binary translation?

It might be, its been a while since I got ESXi to use VMX on KVM. Take
a look at the VMware log file for the L2, it should have a lot more
information.

Cheers,
Muli

      parent reply	other threads:[~2014-06-03 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+g7VZ3kFEGjeiQLnoK4GFAYU4=Y-4HU1gzz15A-sCO406qekQ@mail.gmail.com>
2014-06-01 10:59 ` [Qemu-devel] Nested KVM is weird? Muli Ben-Yehuda
     [not found]   ` <CA+g7VZ05M3NV11A1c4tsnAuBCdvdnirOk-==s2rP1MrrpU909g@mail.gmail.com>
2014-06-03 10:53     ` Muli Ben-Yehuda [this message]

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=20140603105350.GA9296@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