From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: solarflare.com, ip: 148.163.129.52, mailfrom: tpilar@solarflare.com) Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [148.163.129.52]) by groups.io with SMTP; Wed, 29 May 2019 02:44:16 -0700 X-Virus-Scanned: Proofpoint Essentials engine Received: from webmail.solarflare.com (webmail.solarflare.com [12.187.104.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1-us1.ppe-hosted.com (PPE Hosted ESMTP Server) with ESMTPS id D50C2B40055; Wed, 29 May 2019 09:44:14 +0000 (UTC) Received: from tp-desktop.uk.solarflarecom.com (10.17.20.51) by ocex03.SolarFlarecom.com (10.20.40.36) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 29 May 2019 02:44:11 -0700 Subject: Re: [edk2-devel] OVMF and SMBIOS To: , References: <16be83ee265e46db88af85dc47949e23@ukex01.SolarFlarecom.com> From: "Tomas Pilar (tpilar)" Message-ID: <16ce9884-f42e-eefc-062e-a23fdf680b2d@solarflare.com> Date: Wed, 29 May 2019 10:44:09 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: X-Originating-IP: [10.17.20.51] X-TM-AS-Product-Ver: SMEX-12.5.0.1300-8.5.1010-24644.005 X-TM-AS-Result: No-15.514900-4.000000-10 X-TMASE-MatchedRID: gjZGo2H/wj/mLzc6AOD8DfHkpkyUphL9w3BtuOFz4BGmBkXli2IfBKAs suKVAEQ36j33+BFSF5h8XOC51rQ7FYJiSQkXWLNVqjZ865FPtpqsU/iX0A2wj9xSVCzxgUrO2XA Gc2BjwwuggnC4SsEPF8qhBmdRNkjGwqMyRAqToWMlPLVu9PurrVsP0tBwe3qDJt7ZZwvxOlRxWi UYx2RYG9zaad7ROSD8AEjOD2KPH1Mm2WWAELvR+X4neC0h7SAD+KgiyLtJrSD99KEd45s5KpyGB OWQ2FtLQrSBnAN/YDEcKPHe9QJyLEkfXU45UHTJTSMhEUhjtjUr9gVlOIN/6ubnFWpNX1DBBClh B0TZdJiy0eK+KXVK1KldHs0DobMiwdU14NatZIYNwUVhIF6pVgRryDXHx6oXw62uSG5kL1bCCAd NMPTZJ3NLfHcK72CBVZ/agdQpzSEIA+AvHJUe1VSzRMNv1fRD4oSd18bdmwJIXJo+eGm+FOJTPN 6INtjYgt2z3xIftvt+WakqvGWIwo9oUcx9VMLgOX/V8P8ail3BxqsKSczjIvoA9r2LThYYKrauX d3MZDV2EHmbm9v91MurRc498gVnqGEukCcnh/yxI0DkufC2Gjtyyx/FFjQv X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--15.514900-4.000000 X-TMASE-Version: SMEX-12.5.0.1300-8.5.1010-24644.005 X-MDID: 1559123055-DG-QUDJgfsmz Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Content-Language: en-US On 28/05/2019 18:06, Laszlo Ersek wrote: > On 05/28/19 17:18, Tomas Pilar (tpilar) wrote: >> Hi, >> >> I am trying to create kvm instance using libvirt and Qemu and OVMF that also has SMBIOS included. My current version of Qemu only supports type 0 and type 1 SMBIOS tables so I specify those. However, when I use smbiosview in the UEFI shell, I get back "SMBIOS not found". >> >> I attach my current libvirt xml specification for the kvm host. >> >> Does anyone have any immediate ideas? > The SMBIOS fw_cfg interface between QEMU and guest firmware was reworked > in the QEMU v2.1.0 release (primarily in commit c97294ec1b9e, "SMBIOS: > Build aggregate smbios tables and entry point", 2014-05-05). > > If you use an earlier QEMU release, or else you use a machine type > earlier than pc-i440fx-2.1, then the new SMBIOS fw_cfg interface is not > exposed to guest firmware. > > And, upstream OVMF never gained patches for the "legacy" SMBIOS fw_cfg > interface. I had posted patches for that in 2013, but they were not > accepted. The thread starts here: > > [edk2] [PATCH 0/3] OvmfPkg: basic SMBIOS support on QEMU > https://www.mail-archive.com/edk2-devel@lists.sourceforge.net/msg02917.html > > We (RH) carried forward these patches for quite some time in RHEL7 and > (IIRC) Fedora as well, but QEMU v2.1.0 was released in Aug 2014 if I > read the git log right, and so we too dropped the downstream-only > patches at some point, in favor of the new interface. > > Based on your libvirt domain xml... It looks likely that you use the > qemu-kvm package that is part of base RHEL7. That package is based on > upstream QEMU 1.5.3, and so it indeed lacks support for the "new" SMBIOS > interface. If you can use CentOS, you could try the qemu-kvm-ev package > instead. (That one is based on upstream 2.12.) > > Alternatively, you could check the "OVMF-20160202-2.gitd7c0dfa.el7" > package (or earlier), which should (a) still include the > above-referenced patches, and (b) still run on the 1.5.3-based qemu-kvm > emulator. (Later OVMF packages would only provide the SMM_REQUIRE > firmware binary, which does not boot on the 1.5.3-based qemu-kvm emulator.) > > Thanks > Laszlo Thank you Laszlo, that was incredibly thorough! I should be able to work with this. Cheers, Tom