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 bugzilla.redhat.com.
Bug 2057769
| Summary: | missing 'nvram-template' when start ovmf guest | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Meina Li <meili> | |
| Component: | libvirt | Assignee: | Daniel Berrangé <berrange> | |
| libvirt sub component: | General | QA Contact: | Meina Li <meili> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | high | CC: | amurdaca, berrange, coli, hongzliu, jdenemar, jieli, jiji, jsuchane, juzhou, kraxel, lcheng, ldoktor, lmiccini, lpivarc, mhou, mpitt, obudai, pbonzini, perobins, pkrempa, pvlasin, rjones, rpittau, virt-maint, xiaofwan, xiawu, xuwei, xuzhang, xzhou, yfu, yicui, yoguo, zixchen | |
| Version: | 9.0 | Keywords: | Automation, Regression, TestBlocker, Triaged | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | libvirt-8.0.0-6.el9 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2060776 (view as bug list) | Environment: | ||
| Last Closed: | 2022-05-17 12:46:34 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 910269, 1943296, 1922007, 2060776 | |||
The following patch (which is merged upstream) will avoid the immediate error https://listman.redhat.com/archives/libvir-list/2022-February/msg00670.html Actual support for SEV measurement,w hich will use the new EDK firmware build, is tracked in bug 2058004 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. Can start the ovmf guest successfully in libvirt-8.1.0-1.fc35.x86_64 with the fixed patch in comment 2. (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. *** 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. *** Bug 2059043 has been marked as a duplicate of this bug. *** RHEL-9.0.0 fix at https://gitlab.com/redhat/rhel/src/libvirt/-/merge_requests/15 (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. *** Bug 2059173 has been marked as a duplicate of this bug. *** Pre-verified with scrach build libvirt-8.0.0-6.el9_rc.1813faedff.x86_64: PASS *** Bug 2059495 has been marked as a duplicate of this bug. *** This also broke cockpit-machines, most tests now fail on CentOS 9 stream and RHEL 9: https://artifacts.dev.testing-farm.io/a880a31c-cf3b-40b3-b97c-460972cf6178/ Is there any known workaround? > Is there any known workaround?
It's enough to do: rm /usr/share/qemu/firmware/50-edk2-ovmf-amdsev.json
(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 *** Bug 2060500 has been marked as a duplicate of this bug. *** *** Bug 2060709 has been marked as a duplicate of this bug. *** Any idea why this is still not fixed in CentOS 9 stream? http://mirror.stream.centos.org/9-stream/AppStream/x86_64/os/Packages/ still has 8.0.0-5. Should't RHEL 9 fixes go via c9s? 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?