Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1335395 - Add paths for UEFI from new edk2-ovmf package
Summary: Add paths for UEFI from new edk2-ovmf package
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARM64, F-ExcludeArch-aarch64
TreeView+ depends on / blocked
Reported: 2016-05-12 07:37 UTC by Marcin Juszkiewicz
Modified: 2016-05-31 17:35 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-05-20 21:34:26 UTC
Type: Bug

Attachments (Terms of Use)

Description Marcin Juszkiewicz 2016-05-12 07:37:04 UTC
Description of problem:

libvirt has paths to UEFI blobs in /etc/libvirt/qemu.conf file:

 nvram = [

This path is for package from Kraxel firmware repository and we recently got edk2-ovmf (and edk2-aavmf on aarch64) built for F24 and F25 which keep files in /usr/share/edk2/ subdirectories.

So libvirt needs to have new paths added.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

Actual results:

With new UEFI builds installed and no Kraxel repo ones none of VM works.

Expected results:

Libvirt tools use UEFI blobs from edk2-{ovmf,aavmf} packages.

Additional info:

Comment 1 Peter Robinson 2016-05-17 19:17:15 UTC
Cole: can you look at that so the shipped Tianocore uEFI for aarch64 is used for F-24 please?

Comment 2 Cole Robinson 2016-05-20 21:34:26 UTC
Fixed in libvirt-1.3.4-2.fc25

Note You need to log in before you can comment on or make changes to this bug.