[PATCH 0/2] [RfC] edk2: add qemu variable store firmware builds

[PATCH 0/2] [RfC] edk2: add qemu variable store firmware builds

[Gerd Hoffmann]

This is somewhat related to the bigger question how we want move forward
with firmware builds in the qemu repo ...

qemu got uefi variable store support in version 10.0.  With the pending
edk2 firmware update (patches are on the list right now) edk2 is new
enough that support for the qemu variable store is present in the code
base.  This is a compile time option though, so it needs separate
firmware images.  This little patch series adds them.

The big question is if we want go down that route.  The images are not
essential for qemu itself.  The test cases for the acpi tables use the
firmware images for the traditional, pflash-based efi variable store
and can continue to do so.

So, do we want add them?  For qemu developer / user convenience?  Or
leave that to linux distributions?  Fedora already ships builds (see
/usr/share/edk2/*/*qemuvars*).

take care,
  Gerd

Gerd Hoffmann (2):
  edk2: add qemuvars builds to config
  edk2: add qemuvars build binaries

 pc-bios/edk2-aarch64-qemuvars.fd.bz2 | Bin 0 -> 1621714 bytes
 pc-bios/edk2-x86_64-qemuvars.fd.bz2  | Bin 0 -> 2095693 bytes
 roms/edk2-build.config               |  37 +++++++++++++++++++++++++++
 3 files changed, 37 insertions(+)
 create mode 100644 pc-bios/edk2-aarch64-qemuvars.fd.bz2
 create mode 100644 pc-bios/edk2-x86_64-qemuvars.fd.bz2

-- 
2.52.0

[PATCH 1/2] edk2: add qemuvars builds to config

[Gerd Hoffmann]

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
 roms/edk2-build.config | 37 +++++++++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)

diff --git a/roms/edk2-build.config b/roms/edk2-build.config
index 96ebc3bcd9e7..9caafa7a5f55 100644
--- a/roms/edk2-build.config
+++ b/roms/edk2-build.config
@@ -20,6 +20,11 @@ SECURE_BOOT_ENABLE       = TRUE
 SMM_REQUIRE              = TRUE
 BUILD_SHELL              = FALSE
 
+[opts.ovmf.sb.qemuvars]
+SECURE_BOOT_ENABLE       = TRUE
+QEMU_PV_VARS             = TRUE
+BUILD_SHELL              = FALSE
+
 [opts.armvirt.silent]
 DEBUG_PRINT_ERROR_LEVEL  = 0x80000000
 
@@ -55,6 +60,16 @@ plat = OvmfX64
 dest = ../pc-bios
 cpy1 = FV/OVMF_CODE.fd edk2-x86_64-secure-code.fd
 
+[build.ovmf.x86_64.qemuvars]
+desc = ovmf build (64-bit, secure boot)
+conf = OvmfPkg/OvmfPkgX64.dsc
+arch = X64
+opts = common
+       ovmf.sb.qemuvars
+plat = OvmfX64
+dest = ../pc-bios
+cpy1 = FV/OVMF.fd edk2-x86_64-qemuvars.fd
+
 [build.ovmf.microvm]
 desc = ovmf build for microvm
 conf = OvmfPkg/Microvm/MicrovmX64.dsc
@@ -81,6 +96,19 @@ cpy2 = FV/QEMU_VARS.fd edk2-aarch64-vars.fd
 pad1 = edk2-aarch64-code.fd  64m
 pad2 = edk2-aarch64-vars.fd  64m
 
+[build.armvirt.aa64.qemuvars]
+desc = ArmVirt build, 64-bit (arm v8)
+conf = ArmVirtPkg/ArmVirtQemu.dsc
+arch = AARCH64
+opts = common
+       armvirt.silent
+       ovmf.sb.qemuvars
+pcds = nx.broken.shim.grub
+plat = ArmVirtQemu-AArch64
+dest = ../pc-bios
+cpy1 = FV/QEMU_EFI.fd  edk2-aarch64-qemuvars.fd
+pad1 = edk2-aarch64-qemuvars.fd  64m
+
 ####################################################################################
 # riscv64
 
@@ -94,6 +122,15 @@ cpy2 = FV/RISCV_VIRT_VARS.fd  edk2-riscv64-vars.fd
 pad1 = edk2-riscv64-code.fd   32m
 pad2 = edk2-riscv64-vars.fd   32m
 
+#[build.riscv.qemu.qemuvars]
+#conf = OvmfPkg/RiscVVirt/RiscVVirtQemu.dsc
+#arch = RISCV64
+#opts = ovmf.sb.qemuvars
+#plat = RiscVVirtQemu
+#dest = ../pc-bios
+#cpy1 = FV/RISCV_VIRT_CODE.fd  edk2-riscv-qemuvars.fd
+#pad1 = edk2-riscv-qemuvars.fd     32m
+
 ####################################################################################
 # LoongArch64
 
-- 
2.52.0

Re: [PATCH 0/2] [RfC] edk2: add qemu variable store firmware builds

[Philippe Mathieu-Daudé]

Cc'ing Michael and Daniel

On 28/11/25 10:25, Gerd Hoffmann wrote:
> This is somewhat related to the bigger question how we want move forward
> with firmware builds in the qemu repo ...
> 
> qemu got uefi variable store support in version 10.0.  With the pending
> edk2 firmware update (patches are on the list right now) edk2 is new
> enough that support for the qemu variable store is present in the code
> base.  This is a compile time option though, so it needs separate
> firmware images.  This little patch series adds them.
> 
> The big question is if we want go down that route.  The images are not
> essential for qemu itself.  The test cases for the acpi tables use the
> firmware images for the traditional, pflash-based efi variable store
> and can continue to do so.
> 
> So, do we want add them?  For qemu developer / user convenience?  Or
> leave that to linux distributions?  Fedora already ships builds (see
> /usr/share/edk2/*/*qemuvars*).
> 
> take care,
>    Gerd
> 
> Gerd Hoffmann (2):
>    edk2: add qemuvars builds to config
>    edk2: add qemuvars build binaries
> 
>   pc-bios/edk2-aarch64-qemuvars.fd.bz2 | Bin 0 -> 1621714 bytes
>   pc-bios/edk2-x86_64-qemuvars.fd.bz2  | Bin 0 -> 2095693 bytes
>   roms/edk2-build.config               |  37 +++++++++++++++++++++++++++
>   3 files changed, 37 insertions(+)
>   create mode 100644 pc-bios/edk2-aarch64-qemuvars.fd.bz2
>   create mode 100644 pc-bios/edk2-x86_64-qemuvars.fd.bz2
>