Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
missing 'nvram-template' when start ovmf guest
Version-Release number of selected component (if applicable):
libvirt-8.0.0-4.el9.x86_64
qemu-kvm-6.2.0-9.el9.x86_64
edk2-ovmf-20220126gitbb1bba3d77-3.el9.noarch
How reproducible:
100%
Steps to Reproduce:
1. Prepare a ovmf guest.
# virsh edit ovmf
...
<os firmware='efi'>
<type arch='x86_64' machine='pc-q35-rhel9.0.0'>hvm</type>
<boot dev='hd'/>
</os>
...
2. Start the ovmf guest.
# virsh start lmn
setlocale: No such file or directory
error: Failed to start domain 'lmn'
error: internal error: missing 'nvram-template' in '/usr/share/qemu/firmware/50-edk2-ovmf-amdsev.json'
Actual results:
As step 2.
Expected results:
Can start successfully.
Additional info:
Before we have /usr/share/qemu/firmware/50-edk2-ovmf-cc.json for sev feature. Why we had another 50-edk2-ovmf-amdsev.json?
Can start the ovmf guest successfully in libvirt-8.1.0-1.fc35.x86_64 with the fixed patch in comment 2.
Comment 7Jaroslav Suchanek
2022-02-25 12:18:27 UTC
(In reply to Xuesong Zhang from comment #5)
> Hi, Jarda,
>
> From QE's POV, we suggest to fix this regression and testblocker in 9.0.0,
> please have a look and set the ITR, thanks.
ITR set.
Comment 10Jaroslav Suchanek
2022-02-25 15:19:13 UTC
*** Bug 2058618 has been marked as a duplicate of this bug. ***
Hello guys, probably obvious note but this also affects "virt-resize" and similar commands, therefore until this is resolved the nightly perf-ci is blocked by this.
(In reply to Lukáš Doktor from comment #11)
> Hello guys, probably obvious note but this also affects "virt-resize" and
> similar commands, therefore until this is resolved the nightly perf-ci is
> blocked by this.
The impact is on any app that attempts to use guests that are configured with UEFI firmware, so pretty much any & all virt apps.
(In reply to Martin Pitt from comment #21)
> > Is there any known workaround?
>
> It's enough to do: rm /usr/share/qemu/firmware/50-edk2-ovmf-amdsev.json
If you don't want to touch files owned by RPM an alternative is
touch /etc/qemu/firmware/50-edk2-ovmf-amdsev.json
which will hide the RPM installed file
Comment 26Masayoshi Mizuma (Fujitsu)
2022-03-04 14:32:17 UTC
*** Bug 2060500 has been marked as a duplicate of this bug. ***
Comment 27Richard W.M. Jones
2022-03-04 17:23:03 UTC
*** Bug 2060709 has been marked as a duplicate of this bug. ***
Because CentOS 9 Stream already tracks RHEL 9.1 rather than RHEL 9.0 and there
was no libvirt-8.0.0-6.el9 build in 9.1. Libvirt was rebased to 8.1.0 there
instead, i.e., 9.1 should include libvirt-8.1.0-1.el9 with the fix included,
but unfortunately the build did not finish gating yet.
(In reply to Jiri Denemark from comment #30)
> Because CentOS 9 Stream already tracks RHEL 9.1 rather than RHEL 9.0 and
> there
> was no libvirt-8.0.0-6.el9 build in 9.1. Libvirt was rebased to 8.1.0 there
> instead, i.e., 9.1 should include libvirt-8.1.0-1.el9 with the fix included,
> but unfortunately the build did not finish gating yet.
The gating of libvirt-8.1 is failed by BZ 2064115. Even you get the libvirt-8.1 build, the issue in this BZ is fixed, but you will met another issue in BZ 2064115.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (new packages: libvirt), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:2390
Description of problem: missing 'nvram-template' when start ovmf guest Version-Release number of selected component (if applicable): libvirt-8.0.0-4.el9.x86_64 qemu-kvm-6.2.0-9.el9.x86_64 edk2-ovmf-20220126gitbb1bba3d77-3.el9.noarch How reproducible: 100% Steps to Reproduce: 1. Prepare a ovmf guest. # virsh edit ovmf ... <os firmware='efi'> <type arch='x86_64' machine='pc-q35-rhel9.0.0'>hvm</type> <boot dev='hd'/> </os> ... 2. Start the ovmf guest. # virsh start lmn setlocale: No such file or directory error: Failed to start domain 'lmn' error: internal error: missing 'nvram-template' in '/usr/share/qemu/firmware/50-edk2-ovmf-amdsev.json' Actual results: As step 2. Expected results: Can start successfully. Additional info: Before we have /usr/share/qemu/firmware/50-edk2-ovmf-cc.json for sev feature. Why we had another 50-edk2-ovmf-amdsev.json?