Description of problem: When creating vm pool, the Chipset/Firmware Type setting doesn't take effect, the created pool's actual Chipset/Firmware Type is different from the setting value. Version-Release number of selected component (if applicable): ovirt-engine-4.4.6.5-0.17.el8ev.noarch How reproducible: 100% Steps to Reproduce: 1. Prepare Cluster and VM template: - Cluster's compatibility version is 4.6, Chipset/Firmware Type is Q35 Chipset with BIOS - The VM template's Chipset/Firmware Type is Q35 Chipset with BIOS(the test used latest-rhel-guest-image-8.3-infra) 2. Create VM pool: - Cluster: the prepared Cluster - Template: the prepared template - Number of VMs: 1 - Prestarted VMs: 0 - Maximum number of VMs per user: 1 - Chipset/Firmware Type: select one of the following values, I440FX Chipset with BIOS Q35 Chipset with UEFI Q35 Chipset with UEFI SecureBoot 3. Check the VM pool's Chipset/Firmware Type after it's created. Actual results: 1. VM pool's actual Chipset/Firmware Type is always Q35 Chipset with BIOS, regardless which type is set at the time of creation. Expected results: 1. VM pool's actual Chipset/Firmware Type should be the same as the value selected when creating the pool. Additional info:
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Verified with: ovirt-engine-4.4.6.6-0.10.el8ev.noarch Steps: The same as steps in Bug Description. Results: VM pool's actual Chipset/Firmware Type is the same as the value selected when creating the pool.
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.6 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.