From: Laszlo Ersek <lersek@redhat.com>
To: Patchmail <patchmail@gmail.com>
Cc: edk2-devel@lists.01.org, Ladi Prosek <lprosek@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: EDK2 + VT-x
Date: Thu, 14 Sep 2017 11:23:46 +0200 [thread overview]
Message-ID: <99efd8c4-4450-7904-3622-24219d94add5@redhat.com> (raw)
In-Reply-To: <CAKKbd57JieHNRZ=7w5R6SOHOTk3kEADhtAR3a7WUhOs=2mqEiw@mail.gmail.com>
CC Ladi and Eduardo
On 09/14/17 02:54, Patchmail wrote:
> I cannot find anywhere how to enable VT-x in OVMF, if anyone can point me
> in the right direction, I'd greatly appreciate it.
If you are looking to do nested virt with OVMF, first of all I recommend
the following blog to your attention:
https://ladipro.wordpress.com/
I think Eduardo must have a bunch of blog posts on CPU models as well:
https://habkost.net/
Second, if you add the +vmx flag to your CPU model on the QEMU command
line, or in the libvirt domain XML, then QEMU will expose that to OVMF
in a dedicated fw_cfg file ("etc/msr_feature_control"), and OVMF will
set the Feature Control MSR accordingly, on all the CPUs in the guest.
Please refer to the following:
- TianoCore BZ <https://bugzilla.tianocore.org/show_bug.cgi?id=86>
- edk2 commit dbab994991c7 ("OvmfPkg/PlatformPei: program
MSR_IA32_FEATURE_CONTROL from fw_cfg", 2016-07-07).
IOW, with the caveats described in Ladi's and Eduardo's blogs, just add
the +vmx flag to your CPU model, and you should be good to go.
Thanks
Laszlo
next prev parent reply other threads:[~2017-09-14 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 0:54 EDK2 + VT-x Patchmail
2017-09-14 9:23 ` Laszlo Ersek [this message]
2017-09-14 13:30 ` Patchmail
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-list 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=99efd8c4-4450-7904-3622-24219d94add5@redhat.com \
--to=devel@edk2.groups.io \
/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