MAAS should install qemu-efi-aarch64 on arm64 KVM pods
Bug #1916073 reported by
Lee Trager
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Undecided
|
Lee Trager | ||
2.9 |
Won't Fix
|
Undecided
|
Lee Trager | ||
qemu (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
I used MAAS to deploy a VM host. When MAAS does this it installs the libvirt-
Failed to open file '/usr/share/
Manually installing the qemu-efi package fixes the issue.
AMD64 and PPC64 don't require the qemu-efi package because by default they don't emulate UEFI. Because ARM64 does emulate UEFI by default the qemu-efi package should be required by qemu-system-arm.
Related branches
~ltrager/maas:lp1916073_2.9
- Lee Trager (community): Approve
-
Diff: 68 lines (+31/-2)2 files modifiedsrc/metadataserver/tests/test_vendor_data.py (+26/-1)
src/metadataserver/vendor_data.py (+5/-1)
~ltrager/maas:lp1916073
- Lee Trager (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 68 lines (+31/-2)2 files modifiedsrc/metadataserver/tests/test_vendor_data.py (+26/-1)
src/metadataserver/vendor_data.py (+5/-1)
Changed in maas: | |
milestone: | none → 2.10-beta1 |
status: | In Progress → Fix Committed |
summary: |
- qemu-system-arm should depend on qemu-efi + MAAS should install qemu-efi-aarch64 on arm64 KVM pods |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi Lee o/,
qemu-efi is only a transitional anymore.
It depends on and was replaced by qemu-efi-aarch64.
And qemu-system-arm already has a Recommends on ... qemu-efi-aarch64, qemu-efi-arm
Since the default is to install Recommends that should already be no issue.
There are use cases for qemu-system-arm without qemu-efi-aarch64 and we had bugs and discussions that imply making it a Depends causes problems for others.
Therefore I wonder what happened that this wasn't pulled in by default.
I've double checked Focal / Hirsute (what release are you on BTW?)
root@test- qemu-dep- h:~# apt install qemu-system-arm | grep -- qemu-efi
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
publicsuffix qemu-block-extra qemu-efi-aarch64 qemu-efi-arm qemu-dep- h:~# apt install libvirt- daemon- system | grep -- qemu-efi
publicsuffix qemu-block-extra qemu-efi-aarch64 qemu-efi-arm qemu-system-arm
^C
root@test-
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
qemu-block-extra qemu-efi-aarch64 qemu-efi-arm qemu-system-arm
parted policykit-1 publicsuffix qemu-block-extra qemu-efi-aarch64
qemu-efi-arm qemu-system-arm qemu-system-common qemu-system-data
^C
root@test- qemu-dep- f:~# apt install qemu-system-arm | grep -- qemu-efi
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
qemu-efi-aarch64 qemu-efi-arm qemu-system-common qemu-system-data qemu-dep- f:~# apt install libvirt- daemon- system | grep -- qemu-efi
qemu-efi-aarch64 qemu-efi-arm qemu-system-arm qemu-system-common
^C
root@test-
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
qemu-efi-aarch64 qemu-efi-arm qemu-kvm qemu-system-arm qemu-system-common
qemu-efi-aarch64 qemu-efi-arm qemu-kvm qemu-system-arm qemu-system-common
^C
You see it is pulled in from libvirt- daemon- system as well as from qemu-system-arm?
So we can't make it stronger (depends) and I can not reproduce it over here.
Something is different on your test environment, do you know what?