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.
DescriptionAndrea Bolognani
2020-09-18 13:32:04 UTC
+++ This bug was initially created as a clone of Bug #1852910 +++
This bug is quite similar to bug 1776949, but instead of getting the
"unable to find any master var store for loader" message at install
time, we get it at live migration time. The same workaround from bug
1776949 comment 1 works to fix migration, even though it's no longer
necessary to fix install.
--- Additional comment from Michal Privoznik on 2020-09-08 17:28:30 UTC ---
Patch posted upstream:
https://www.redhat.com/archives/libvir-list/2020-September/msg00465.html
--- Additional comment from Michal Privoznik on 2020-09-09 12:49:52 UTC ---
Merged upstream as:
c43622f06e qemuFirmwareFillDomain: Fill NVRAM template on migration too
v6.7.0-112-gc43622f06e
Luiz wondered whether this would affect x86_64 in addition to
aarch64, and as it turns out it does: if your guest definition looks
like
<domain type='kvm'>
<os>
<type arch='x86_64' machine='pc-q35-rhel8.2.0'>hvm</type>
<loader readonly='yes' secure='yes' type='pflash'>/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/guest_VARS.fd</nvram>
</os>
...
which is what you'd get out of a virt-install call along the lines of
$ virt-install --os-variant rhel8.0 --boot uefi ...
then you'll experience the same issue on migration:
$ virsh migrate guest qemu+ssh://dst/system
error: operation failed: unable to find any master var store for loader: /usr/share/edk2/ovmf/OVMF_CODE.secboot.fd
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 (Moderate: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), 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/RHSA-2021:1762