Bug 1865883
| Summary: | aarch64: migration failure: unable to find any master var store for loader | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | Andrew Jones <drjones> | ||||
| Component: | libvirt | Assignee: | Virtualization Maintenance <virt-maint> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 8.2 | CC: | abologna, lcapitulino, mprivozn, virt-maint | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 8.3 | ||||||
| Hardware: | aarch64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-09-09 07:29:16 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: | 1825378 | ||||||
| Attachments: |
|
||||||
|
Description
Andrew Jones
2020-08-04 12:48:35 UTC
Please include the domain XML as well as version numbers for all virtualization components on both sides of the migration. Created attachment 1710966 [details]
domain xml
Both machines have the same packages installed
libvirt-6.6.0-2.module+el8.3.0+7567+dc41c0a9.aarch64
qemu-kvm-5.0.0-2.module+el8.3.0+7379+0505d6ca.aarch64
edk2-aarch64-20200602gitca407c7246bf-2.el8.noarch
virt-install-2.2.1-3.el8.noarch
Installed the guest with
virt-install -n guest -l /path/to/latest/rhel8 --vcpus 16 --disk size=6 --memory 4096 --network bridge=br0
Migrated with
virsh migrate --live --verbose rhel8 qemu+ssh://$PEER/system
/var/lib/libvirt/images/ is an NFS share
I managed to reproduce this today, with zero setup.
We should not hit that error message, since there is a firmware
definition file on the system that clearly defines the relationship
between the firmware image in use and the corresponding varstore
template:
$ cat /usr/share/qemu/firmware/60-edk2-aarch64.json
{
"description": "UEFI firmware for ARM64 virtual machines",
"interface-types": [
"uefi"
],
"mapping": {
"device": "flash",
"executable": {
"filename": "/usr/share/edk2/aarch64/QEMU_EFI-silent-pflash.raw",
"format": "raw"
},
"nvram-template": {
"filename": "/usr/share/edk2/aarch64/vars-template-pflash.raw",
"format": "raw"
}
},
"targets": [
{
"architecture": "aarch64",
"machines": [
"virt-*"
]
}
],
"features": [
],
"tags": [
]
}
My current theory is that the file is not being parsed for some
reason, and this hardcoded list from src/qemu/qemu_conf.c ends up
being used instead:
#ifndef DEFAULT_LOADER_NVRAM
# define DEFAULT_LOADER_NVRAM \
"/usr/share/OVMF/OVMF_CODE.fd:/usr/share/OVMF/OVMF_VARS.fd:" \
"/usr/share/OVMF/OVMF_CODE.secboot.fd:/usr/share/OVMF/OVMF_VARS.fd:" \
"/usr/share/AAVMF/AAVMF_CODE.fd:/usr/share/AAVMF/AAVMF_VARS.fd:" \
"/usr/share/AAVMF/AAVMF32_CODE.fd:/usr/share/AAVMF/AAVMF32_VARS.fd"
#endif
This would explain why pointing to AAVMF_CODE.fd makes things work.
Note that
$ ls -l /usr/share/AAVMF/AAVMF_CODE.fd
lrwxrwxrwx. 1 root root 42 Aug 10 02:44 /usr/share/AAVMF/AAVMF_CODE.fd -> ../edk2/aarch64/QEMU_EFI-silent-pflash.raw
so it's literally the same file we're talking about.
I'll investigate further, and hopefully get to the bottom of it all,
next week.
I think this is a dup of bug 1852910. It has the same symptoms. (In reply to Michal Privoznik from comment #7) > I think this is a dup of bug 1852910. It has the same symptoms. Indeed. Sorry Andrea, I completely forgot that I had already reported this. Closing as duplicate. *** This bug has been marked as a duplicate of bug 1852910 *** |