Bug 1782778
Summary: | virt-install unable to find any master var store for loader | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sampson Fung <sampsonfung> |
Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | agedosier, awilliam, berrange, bugzilla, clalancette, crobinso, itamar, jforbes, laine, libvirt-maint, phrdina, pmarciniak, pwhalen, robatino, veillard, virt-maint |
Target Milestone: | --- | Keywords: | Upstream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-02-03 17:44:31 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: | 1705303 |
Description
Sampson Fung
2019-12-12 10:29:48 UTC
Hi, thanks for the report. The issue is in libvirt where we introduced firmware autoselection feature which broke this old way of specifying UEFI firmwares that virt-install currently uses. Moving to libvirt to get it fixed there. Patches proposed on the upstream list: https://www.redhat.com/archives/libvir-list/2019-December/msg01076.html Proposed as a Blocker for 32-beta by Fedora user chrismurphy using the blocker tracking app because: Beta: "The release must be able host virtual guest instances of the same release. What does that mean? This rather concise criterion means effectively means that both virtual host and virtual guest functionality must work - it's implied, if you think about it. It also means that there must be no showstopper bugs in the installer when installing to a virtual machine..." There isn't an explicit UEFI release criterion, but I think it's implied (?) just because we've got openQA tests that depend on it, and at this point it's basic enough I think it's fair to say such breakage should be blocked on until fixed. Adam Williamson points out Basic Criterion most likely applies here: "All release-blocking images must boot in their supported configurations." And this has an expanded clarification that includes UEFI. Patches mentioned in comment 4 are for qemu, should the bug component be changed to qemu so this can get fixed? qemu-kvm-4.2.0-2.fc32.x86_64 libvirt-daemon-kvm-5.10.0-2.fc32.x86_64 (In reply to Chris Murphy from comment #7) > Patches mentioned in comment 4 are for qemu, should the bug component be > changed to qemu so this can get fixed? I don't think they are meant for qemu. They were sent to the libvirt list. True, they mention qemu but that doesn't mean they are meant for qemu. Libvirt is the right component. In fact, I've sent v2: https://www.redhat.com/archives/libvir-list/2020-January/msg00231.html I've pushed patches upstream: 8e1804f9f6 qemu_firmware: Try to autofill for old style UEFI specification 7c5264d2be src: Introduce and use virDomainDefHasOldStyleUEFI() and virDomainDefHasOldStyleROUEFI() 57f9067ca3 qemu_firmware: Introduce @want variable to qemuFirmwareMatchDomain() 50d7465f3d qemu_firmware: Pass virDomainDef into qemuFirmwareFillDomain() v5.10.0-507-g8e1804f9f6 The root issue is in f31 libvirt packages, but it was only exposed by: commit 5a5e92000d12a671f491c5fb90677f63b1ae7e75 Author: Jim Fehlig <jfehlig> Date: Thu Nov 14 09:06:43 2019 -0700 spec: Remove build-time list of edk2 firmwares Which is not in f31, so things work fine there. rawhide will be fixed in a few days when libvirt 6.0.0 is out This is fixed on aarch64 with libvirt-6.0.0-1.fc32 UEFI VMs are working for me. libvirt-daemon-6.0.0-1.fc32.x86_64 qemu-kvm-4.2.0-2.fc32.x86_64 |