Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1854034

Summary:	Show bios type in VM/Template/Pool general information
Product:	[oVirt] ovirt-engine	Reporter:	Arik <ahadas>
Component:	Frontend.WebAdmin	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.1	CC:	bugs, nsimsolo
Target Milestone:	ovirt-4.4.3	Flags:	pm-rhel: ovirt-4.4+
Target Release:	4.4.3.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.3.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-11 06:42:15 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:

Description Arik 2020-07-06 06:55:29 UTC

It can be handy to present the bios type that is configured for a VM in its general information tab for troubleshooting.

If custom bios type is configured for a VM, need to show that type.
If CLUSTER_DEFAULT is configured for a VM, need to show the type along with an indication that it's derived from the cluster settings.

Comment 1 Nisim Simsolo 2020-09-24 07:37:04 UTC

Verified:
ovirt-engine-4.4.3.2-0.19.el8ev

Verification scenario:
1. Create new VMs with the next custom chipset/firmaware type:
Cluster Default (Q35 Chipset with BIOS)
I440FX Chipset with BIOS
Q35 Chipset with BIOS
Q35 Chipset with UEFI
Q35 Chipset with UEFI SecureBoot

2. Browse Webadmin -> VM general tab/templates/pool and verify:
   the correct Chipset/Firmware Type is listed for each VM
   If value is different than cluster default, a warning mouseover icon appears: "The Chipset/Firmware Type does not match the Cluster Chipset/Firmware Type ({0})." 

3. Repeat step 2 for VM templates
4. Repeat step 2 for VM pool

Comment 2 Sandro Bonazzola 2020-11-11 06:42:15 UTC

This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 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.