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.
+++ This bug was initially created as a clone of Bug #1997884 +++
Description of problem:
The Fedora Cloud WG recently changed to offering hybrid boot cloud images. This was done as the start of a longer-term effort to engage with the community and partners to boot Fedora images with UEFI. As part of this effort, we'd like to have the virt stack default to offering UEFI for VMs (with a CSM for BIOS backward compatibility if possible).
It would be appreciated if Cockpit defaulted to creating VMs with UEFI+CSM for "fedora", "unknown linux" and other similar things.
Additional info:
The full discussion about this is in the Fedora Cloud WG meeting logs here: https://meetbot.fedoraproject.org/teams/fedora_cloud_meeting/fedora_cloud_meeting.2021-08-19-14.59.log.html
Comment 3Jaroslav Suchanek
2022-03-30 15:26:14 UTC
The reasonable defaults are usually got from the libosinfo and osinfo-db. For some OSs (win 11) it might be default. For others there could be reason, why uefi is not the default. I think it should be addressed in osinfo-db and not in virt-install part.
Cole, please correct me, if I am wrong. Thanks.
The win11 piece needs pending osinfo-db work: https://gitlab.com/libosinfo/osinfo-db/-/merge_requests/362
Once that's in, virt-manager 4.0.0 will do the right thing and default to UEFI.
What this issue is asking is different though. When an OS supports both UEFI and BIOS, virt-install would still choose BIOS. If we wanted to change that, it's questionable whether it would be an osinfo-db or virt-install change or both.
But, like danpb says over here: https://bugzilla.redhat.com/show_bug.cgi?id=1997882#c2
(In reply to Daniel Berrangé from comment #2)
> Note that using UEFI will break ability to use internal snapshots of VMs.
> This is the main reason why GNOME Boxes only uses UEFI in cases where the
> guest OS does not support legacy BIOS. We have done QEMU work needed to lift
> this limitation, but still need libvirt work done.
There's still blockers to fix before we can consider using UEFI by default in cases where it isn't a hard requirement.
So IMO nothing is going to change here in the short/medium term.