Currently we don't write the actual bios type to the OVF of exported VMs/templates when it's derived from the cluster but we rather write that it's the cluster default. We need to write the effective type the VM is configured with instead.
moving milestone due to dependant bug
Verified using https://bugzilla.redhat.com/show_bug.cgi?id=1855959 workaround (changing the SELinux to permissive): ovirt-engine-4.4.1.8-0.7.el8ev vdsm-4.40.22-1.el8ev.x86_64 libvirt-daemon-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64 qemu-kvm-4.2.0-29.module+el8.2.1+7297+a825794d.x86_64 Verification scenario: 1. Create new cluster with Legacy BIOS Type. 2. Create new VM, keep VM BIOS type with "Cluster Default". Install RHEL 8 on this VM. 3. Export VM as OVA. 4. Extract OVA file and observe vm.ovf file Verify BIOS type is: <BiosType>0</BiosType> 5. Repeat steps 1-3, this time set cluster BIOS type to Q35 Chipset with Legacy BIOS. Verify BIOS type is: <BiosType>1</BiosType> 6. Repeat steps 1-3, this time set cluster BIOS type to Q35 Chipset with UEFI BIOS. Verify BIOS type is: <BiosType>2</BiosType> 7. Repeat steps 1-3, this time set cluster BIOS type to Q35 Chipset with SecureBoot. Verify BIOS type is: <BiosType>3</BiosType> 8. Repeat steps 1-7, this time export template as OVA and observe template.ovf file. 9. Import OVAs and templates (afterward create VMs from these templates) from steps 1-8 and verify import succeeds and VM are running properly.
This bugzilla is included in oVirt 4.4.1.1 Async release, published on July 13th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1.1 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.