From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 7687E21E87993 for ; Thu, 14 Sep 2017 02:20:49 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id DBE9981DF3; Thu, 14 Sep 2017 09:23:47 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com DBE9981DF3 Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=lersek@redhat.com Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-83.rdu2.redhat.com [10.10.120.83]) by smtp.corp.redhat.com (Postfix) with ESMTP id EBA0E17A84; Thu, 14 Sep 2017 09:23:46 +0000 (UTC) To: Patchmail References: Cc: edk2-devel@lists.01.org, Ladi Prosek , Eduardo Habkost From: Laszlo Ersek Message-ID: <99efd8c4-4450-7904-3622-24219d94add5@redhat.com> Date: Thu, 14 Sep 2017 11:23:46 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Thu, 14 Sep 2017 09:23:48 +0000 (UTC) Subject: Re: EDK2 + VT-x X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Sep 2017 09:20:49 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 - 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