Chipset/Firmware Type setting is becoming more important as incorrect setting might cause a VM fail to start or some functionality not to work. The Chipset/Firmware Type field should therefore be on a more visible place than it is at the moment (VM popup dialog -> System tab -> General subsection at the bottom of the dialog).
Verified on RHV 4.5.0-4. Env: - Engine instance with RHV 4.5.0-4 (ovirt-engine-4.5.0-0.237.el8ev) and RHEL 8.6 installed. - 3 hosts with RHV 4.5.0-4 and RHEL 8.6 and with vdsm-4.50.0.10-1.el8ev. Steps: In Admin Portal: 1. Create a 4.7 data center and a 4.7 cluster. 2. Install the hosts and create a new NFS storage domain. 3. In Compute > Virtual Machines, press New. 4. Select an RHEL 8 template as the VM's template. 5. Enter the "System" tab and check that the Chipset/Firmware Type field isn't visible under the General section. 6. Check that the Chipset/Firmware Type field is visible at the top section. 7. Open the field. 8. Check that the available options are: I440FX Chipset with BIOS, Q35 Chipset with BIOS, Q35 Chipset with UEFI, Q35 Chipset with UEFI SecureBoot. 9. Select Q35 Chipset with UEFI. 10. Create the RHEL 8 VM. 11. Enter the VM's page and check that the Chipset/Firmware Type is Q35 Chipset with UEFI. 12. Create a template from the VM. 13. Open the template's edit modal via Compute > Templates > {Template} > Edit 14. Repeat steps 5-8. 15. Open the VM's edit modal via Compute > Virtual Machines > {VM} > Edit. 16. Repeat steps 5-8. 17. Open the VM's clone modal via Compute > Virtual Machines > {VM} > Clone VM. 18. Repeat steps 5-8. 19. Open the VM Pool new modal via Compute > Pools > New. 20. Repeat steps 4-9. 21. Create the pool. 22. Open the pool's edit modal via Compute > Pools > {Pool} > Edit. 23. Repeat steps 5-8. Results (As Expected): 1. The 4.7 data center and the 4.7 cluster were created. 2. The host was installed and the NFS storage domain was created. 3. The VM modal has opened. 4. The RHEL 8 template was selected. 5. The Chipset/Firmware Type field isn't visible in the General section. 6. The field is visible in the top section. 7. The field has opened. 8. The available options are I440FX Chipset with BIOS, Q35 Chipset with BIOS, Q35 Chipset with UEFI, Q35 Chipset with UEFI SecureBoot. 9. The Q35 Chipset with the UEFI chipset was selected. 10. The VM was created. 11. The Chipset/Firmware Type is set Q35 Chipset with UEFI. 12. The template was created. 13. The template's edit modal has opened. 14. The same results as the results for steps 5-8. 15. The VM's edit modal has opened. 16. The same results as the results for steps 5-8. 17. The VM's clone modal has opened. 18. The same results as the results for steps 5-8. 19. The new pool modal has opened. 20. The same results as the results for steps 4-9. 21. The pool was created. 22. The pool's edit modal has opened. 23. The same results as the results for steps 5-8.
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.