From: Alexander Graf <agraf@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH] Add microcode patch level dummy
Date: Mon, 05 Jan 2009 18:08:47 +0100 [thread overview]
Message-ID: <49623E9F.2000008@suse.de> (raw)
In-Reply-To: <496237E5.6050503@codemonkey.ws>
Anthony Liguori wrote:
> Alexander Graf wrote:
>> Anthony Liguori wrote:
>>
>>> Alexander Graf wrote:
>>>
>>>> VMware ESX checks if the microcode level is correct when using a
>>>> barcelona CPU, in
>>>> order to see if it actually can use SVM. Let's tell it we're on the
>>>> safe side...
>>>>
>>> Sounds like you're able to boot ESX? Are you able to run a guest yet?
>>>
>>
>> The moment you wrote the mail I just managed to get ReactOS running in
>> ESX. It does not use SVM yet though. I wonder when/if ESX actually does
>> use SVM.
>>
>
> I'm pretty certain that if ESX detects that it is running under ESX,
> it disables SVM/VT. There was a fair bit of noise a few months ago
> because a certain beta version of VMware didn't do this which meant
> you could no longer run ESX nested. They quickly fixed that.
>
> I'd try disabling vmport and the hypervisor present bit.
Now - that's the issue. VMware tries to detect the CPU TSC speed and
matches if that's a multiple of the bus speed (66Mhz). If not, it panics.
The only way I found around this was to expose the TSC frequency bits to
ESX using the VMware backdoor - but now it thinks it's actually running
inside VMware!
Alex
next prev parent reply other threads:[~2009-01-05 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 15:02 [PATCH] Add microcode patch level dummy Alexander Graf
2009-01-05 16:28 ` Anthony Liguori
2009-01-05 16:30 ` Alexander Graf
2009-01-05 16:38 ` David S. Ahern
2009-01-05 16:39 ` Alexander Graf
2009-01-05 16:40 ` Anthony Liguori
2009-01-05 17:08 ` Alexander Graf [this message]
2009-01-06 9:29 ` 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=49623E9F.2000008@suse.de \
--to=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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).