Package Details: edk2-ovmf-fedora 20260213-1

Git Clone URL: https://aur.archlinux.org/edk2-ovmf-fedora.git (read-only, click to copy)
Package Base: edk2-ovmf-fedora
Description: Firmware for Virtual Machines (x86_64) with Secure Boot enabled — from Fedora 44
Upstream URL: https://packages.fedoraproject.org/pkgs/edk2/edk2-ovmf/
Keywords: bios edk2 efi fedora ovmf qemu secure-boot secureboot uefi
Licenses: MIT, Apache-2.0, BSD-2-Clause-Patent, LicenseRef-Fedora-Public-Domain
Submitter: ryanbarillos
Maintainer: ryanbarillos
Last Packager: ryanbarillos
Votes: 3
Popularity: 0.62
First Submitted: 2025-10-04 13:02 (UTC)
Last Updated: 2026-03-24 17:52 (UTC)

Pinned Comments

ryanbarillos commented on 2026-07-09 11:50 (UTC)

In case anyone needs the up-to-date version of this package, please wait until the end of July as I'll be offline for the next few weeks.

So expect the next update by the end of the month.

ryanbarillos commented on 2025-10-04 13:05 (UTC) (edited on 2025-10-22 10:18 (UTC) by ryanbarillos)

This is the edk2-ovmf package from the Fedora Project.

Purpose?
The purpose of this package is to have an EFI firmare available for all your QEMU virtual machines residing in your local system that includes "Secure Boot" - This is very beneficial for VMs installed with Windows 10-11.

Why?
Currently, the official edk2-ovmf package from the official Arch repo doesn't come with any Secure Boot firmware pre-packaged. This is designed to bridge this gap until the official edk2-ovmf package comes bundled with Secure Boot keys. - For more info, see Arch Wiki section QEMU#Enabling_Secure_Boot

How long will this be maintained?

This package will be kept constantly updated until the the official edk2-ovmf package from the official Arch repo comes bundled with Secure Boot keys, by which point maintaining this package becomes redundant and thus be discontinued from further updates.

How to use this?
1. This package's firmware files will be located at /usr/share/edk2/ovmf
- It's a symbolic link to /usr/share/edk2-ovmf-fedora/edk2/ovmf

2. As for format, you can use the following as your template in your QEMU VM's XML configuration file:

  <os>
    <type arch="x86_64" machine="pc-q35-10.1">hvm</type>
    <loader readonly="yes" type="pflash" format="raw">/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd</loader>
    <nvram template="/usr/share/edk2/ovmf/OVMF_VARS.secboot.fd" format="raw">/var/lib/libvirt/qemu/nvram/win10_VARS.fd</nvram>
  </os>


Final note(s)
For virt-manager users:
- you can conveniently select Fedora's OVMF firmware files from the Firmware dropdown selection & selecting any file beginning with the following:
UEFI x86_64: /usr/share/edk2/ovmf/OVMF*.fd

- If you need Secure Boot, select UEFI x86_64: /usr/share/edk2/ovmf/OVMF_CODE.secboot.fd

Latest Comments

ryanbarillos commented on 2026-07-09 11:50 (UTC)

In case anyone needs the up-to-date version of this package, please wait until the end of July as I'll be offline for the next few weeks.

So expect the next update by the end of the month.

ryanbarillos commented on 2025-10-04 13:05 (UTC) (edited on 2025-10-22 10:18 (UTC) by ryanbarillos)

This is the edk2-ovmf package from the Fedora Project.

Purpose?
The purpose of this package is to have an EFI firmare available for all your QEMU virtual machines residing in your local system that includes "Secure Boot" - This is very beneficial for VMs installed with Windows 10-11.

Why?
Currently, the official edk2-ovmf package from the official Arch repo doesn't come with any Secure Boot firmware pre-packaged. This is designed to bridge this gap until the official edk2-ovmf package comes bundled with Secure Boot keys. - For more info, see Arch Wiki section QEMU#Enabling_Secure_Boot

How long will this be maintained?

This package will be kept constantly updated until the the official edk2-ovmf package from the official Arch repo comes bundled with Secure Boot keys, by which point maintaining this package becomes redundant and thus be discontinued from further updates.

How to use this?
1. This package's firmware files will be located at /usr/share/edk2/ovmf
- It's a symbolic link to /usr/share/edk2-ovmf-fedora/edk2/ovmf

2. As for format, you can use the following as your template in your QEMU VM's XML configuration file:

  <os>
    <type arch="x86_64" machine="pc-q35-10.1">hvm</type>
    <loader readonly="yes" type="pflash" format="raw">/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd</loader>
    <nvram template="/usr/share/edk2/ovmf/OVMF_VARS.secboot.fd" format="raw">/var/lib/libvirt/qemu/nvram/win10_VARS.fd</nvram>
  </os>


Final note(s)
For virt-manager users:
- you can conveniently select Fedora's OVMF firmware files from the Firmware dropdown selection & selecting any file beginning with the following:
UEFI x86_64: /usr/share/edk2/ovmf/OVMF*.fd

- If you need Secure Boot, select UEFI x86_64: /usr/share/edk2/ovmf/OVMF_CODE.secboot.fd

ryanbarillos commented on 2025-10-02 17:50 (UTC)

@Itxaka I appreciate the suggestion! However, I took a different approach by making symbolic links of Fedora's firmare JSON files instead, just to be safe, as well as making a symlink to Fedora's OVMF files at /usr/share/edk2/ovmf

it's not done with ln -sf over concerns of overwriting anything that belongs to "edk2-ovmf" from the official Arch repos (just a regular ln -s).

You can explore this change at the new update available for this package

Itxaka commented on 2025-09-29 07:52 (UTC)

Hi there, thanks for packing this.

We could make this more usable if during build we would fix the fiurmware json files to point to the real package install:

sed -i "s|/usr/share/edk2/ovmf|/usr/share/edk2-ovmf-fedora/OVMF|g" *

That way, if you want to use them for qemu/libvirt you only need to copy the files at /usr/share/edk2-ovmf-fedora/qemu/firmware to /usr/share/qemu/firmware/

Cheers!