Bug 1997884

Summary:	RFE: virt-install: Prefer --boot UEFI for new fedora VMs
Product:	[Fedora] Fedora	Reporter:	Neal Gompa <ngompa13>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	berrange, crobinso, daltonminer, davdunc, davide, dustymabe, fedora, k.koukiou, kkoukiou, mmarusak, mpitt, philip.wyett, pjones, skobyda, sricharan.ramanujam
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1997885 (view as bug list)		Environment:
Last Closed:	2022-02-21 14:18:59 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Neal Gompa 2021-08-26 01:28:10 UTC

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 1 Neal Gompa 2021-08-26 01:58:30 UTC

Here's the ticket for this in the Fedora Cloud WG tracker: https://pagure.io/cloud-sig/issue/345

Comment 2 Martin Pitt 2021-08-26 07:09:02 UTC

@skobyda can you please have a look? I think we get that info from osinfo/virt-install, but it looks like we don't default to UEFI if it's supported?

Comment 3 Simon Kobyda 2021-08-27 13:00:24 UTC

Right now, we don't fetch any information from libosinfo nor we default manually to any firmware during a VM creation, and instead, we just let virt-install to choose correct firmware.
And I don't even think a mapping of preferred firmware to each OS should be implement cockpit. Either virt-install could choose a preferred option, or libosinfo could provide a firmware option in it's list of recommended resource for each OS http://lazka.github.io/pgi-docs/Libosinfo-1.0/classes/Os.html#Libosinfo.Os.get_recommended_resources
I will ping ffidenci about his opinion, if this could instead be implemented for libosinfo

Comment 4 Katerina Koukiou 2021-08-30 11:42:45 UTC

Moved to virt-manager component, so that virt-install can choose the recommended defaults provided by libosinfo/osinfo-db.

Comment 5 Cole Robinson 2022-02-21 14:18:59 UTC

Neal already filed a bug for virt-install/virt-manager, so duping to that one

*** This bug has been marked as a duplicate of bug 1997882 ***