Bug 1997893

Summary:	[RFE] Prefer UEFI for new VMs
Product:	[oVirt] ovirt-engine	Reporter:	Neal Gompa <ngompa13>
Component:	BLL.Virt	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	---	CC:	ahadas, bugs, daltonminer, davdunc, davide, dustymabe, fedora, mavital, mburman, nsimsolo, pjones, sricharan.ramanujam
Target Milestone:	ovirt-4.5.0	Keywords:	FutureFeature
Target Release:	4.5.0	Flags:	pm-rhel: ovirt-4.5? pm-rhel: planning_ack? pm-rhel: devel_ack+ pm-rhel: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-03 06:46:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2021545
Bug Blocks:

Description Neal Gompa 2021-08-26 01:53:50 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 oVirt defaulted to creating VMs with UEFI+CSM for "fedora", "rhel9", "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:56:56 UTC

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

Comment 3 Arik 2021-11-22 12:29:55 UTC

It's just about defaulting new VMs to UEFI (*on latest cluster level*), not changing the bios type on cluster upgrade

Comment 4 Arik 2021-11-22 12:38:01 UTC

Another point discussed is what to do with operating systems that don't support UEFI - to default to BIOS or fail the operation with validation (because the firmware is supposed to be taken from the cluster's definition and the user should change it manually if needed)

Comment 5 Arik 2021-12-20 19:34:09 UTC

(In reply to Arik from comment #4)
> Another point discussed is what to do with operating systems that don't
> support UEFI - to default to BIOS or fail the operation with validation
> (because the firmware is supposed to be taken from the cluster's definition
> and the user should change it manually if needed)

need to default old operating systems to BIOS (like RHEL 5, see https://access.redhat.com/solutions/42632)

Comment 6 Arik 2022-01-03 10:39:10 UTC

(In reply to Arik from comment #5)
> (In reply to Arik from comment #4)
> > Another point discussed is what to do with operating systems that don't
> > support UEFI - to default to BIOS or fail the operation with validation
> > (because the firmware is supposed to be taken from the cluster's definition
> > and the user should change it manually if needed)
> 
> need to default old operating systems to BIOS (like RHEL 5, see
> https://access.redhat.com/solutions/42632)

when provisioning vms/pools the firmware is generally taken from the template so this change only affects new VMs on CL 4.7+ and as those operating systems are not supported, users would need to change the firmware to BIOS if they are selected

Comment 7 Nisim Simsolo 2022-05-02 07:48:18 UTC

Verified:
ovirt-engine-4.5.0.5-0.7.el8ev
vdsm-4.50.0.13-1.el8ev.x86_64
qemu-kvm-6.2.0-11.module+el8.6.0+14707+5aa4b42d.x86_64
libvirt-daemon-8.0.0-5.module+el8.6.0+14480+c0a3aa0f.x86_64

Verification scenario:
1. Verify the default for new VMs chipset/FW type is Q35/UEFI.
2. Verify creation of new VMs with old OS like RHEL 5 is rejected by WebAdmin with an appropriate message 
   ("Cannot add VM. Q35 chipset is not supported by the guest OS Red Hat Enterprise Linux 5.x.") and verify it's possible to create such VMs with I440FX/BIOS.

Comment 8 Sandro Bonazzola 2022-05-03 06:46:19 UTC

This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.