public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Paul Meyer <katexochen0@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/edk2] rawhide: add non-secure-boot TDX firmware descriptor
Date: Wed, 08 Jul 2026 08:06:46 GMT	[thread overview]
Message-ID: <178349800679.1.18351526686261727110.rpms-edk2-bf4e7e94b337@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/edk2
            Branch : rawhide
            Commit : bf4e7e94b337fd294bbd44c0ab027761144c5217
            Author : Paul Meyer <katexochen0@gmail.com>
            Date   : 2026-07-07T10:00:15+02:00
            Stats  : +27/-0 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/edk2/c/bf4e7e94b337fd294bbd44c0ab027761144c5217?branch=rawhide

            Log:
            add non-secure-boot TDX firmware descriptor

Add a firmware descriptor pointing at the already-shipped
OVMF.inteltdx.fd, so QEMU/libvirt firmware autoselection can pick a TDX
firmware without Secure Boot or enrolled keys. Mirrors the sb/nosb pair
already provided for plain OVMF.

Signed-off-by: Paul Meyer <katexochen0@gmail.com>

---
diff --git a/62-edk2-ovmf-x64-inteltdx-nosb.json b/62-edk2-ovmf-x64-inteltdx-nosb.json
new file mode 100644
index 0000000..5e3e5ca
--- /dev/null
+++ b/62-edk2-ovmf-x64-inteltdx-nosb.json
@@ -0,0 +1,23 @@
+{
+    "description": "OVMF with TDX support, no secure boot",
+    "interface-types": [
+        "uefi"
+    ],
+    "mapping": {
+        "device": "memory",
+        "filename": "/usr/share/edk2/ovmf/OVMF.inteltdx.fd"
+    },
+    "targets": [
+        {
+            "architecture": "x86_64",
+            "machines": [
+                "pc-q35-*"
+            ]
+        }
+    ],
+    "features": [
+        "intel-tdx",
+        "verbose-dynamic"
+    ],
+    "tags": []
+}

diff --git a/edk2.spec b/edk2.spec
index e19782a..5a3b1a5 100644
--- a/edk2.spec
+++ b/edk2.spec
@@ -106,6 +106,7 @@ Source46: 51-edk2-ovmf-2m-raw-x64-nosb.json
 Source47: 60-edk2-ovmf-x64-stateless.json
 Source48: 61-edk2-ovmf-x64-amdsev.json
 Source49: 61-edk2-ovmf-x64-inteltdx.json
+Source51: 62-edk2-ovmf-x64-inteltdx-nosb.json
 
 Source50: 50-edk2-riscv-qcow2.json
 
@@ -400,6 +401,7 @@ cp -a -- \
    %{SOURCE20} %{SOURCE21} %{SOURCE22} %{SOURCE23} %{SOURCE24} \
    %{SOURCE40} %{SOURCE41} %{SOURCE42} %{SOURCE43} %{SOURCE44} \
    %{SOURCE45} %{SOURCE46} %{SOURCE47} %{SOURCE48} %{SOURCE49} \
+   %{SOURCE51} \
    %{SOURCE50} \
    %{SOURCE60} \
    %{SOURCE80} %{SOURCE81} %{SOURCE82} %{SOURCE83} %{SOURCE84} \
@@ -634,6 +636,7 @@ install -m 0644 \
         51-edk2-ovmf-2m-raw-x64-nosb.json \
         61-edk2-ovmf-x64-amdsev.json \
         61-edk2-ovmf-x64-inteltdx.json \
+        62-edk2-ovmf-x64-inteltdx-nosb.json \
         %{buildroot}%{_datadir}/qemu/firmware
 %if %{qemuvars}
 install -m 0644 \
@@ -763,6 +766,7 @@ done
 %{_datadir}/qemu/firmware/51-edk2-ovmf-2m-raw-x64-nosb.json
 %{_datadir}/qemu/firmware/61-edk2-ovmf-x64-amdsev.json
 %{_datadir}/qemu/firmware/61-edk2-ovmf-x64-inteltdx.json
+%{_datadir}/qemu/firmware/62-edk2-ovmf-x64-inteltdx-nosb.json
 %if %{qemuvars}
 %{_datadir}/%{name}/ovmf/OVMF.qemuvars.fd
 %{_datadir}/%{name}/ovmf/vars.*.json

                 reply	other threads:[~2026-07-08  8:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178349800679.1.18351526686261727110.rpms-edk2-bf4e7e94b337@fedoraproject.org \
    --to=katexochen0@gmail.com \
    --cc=git-commits@fedoraproject.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