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

Bug 1861963

Summary: BIOS type of non-uefi guest should be 'cluster default' if the guest is imported on rhv4.4 web and bios type of cluster is 'Q35 Chipset with Legacy BIOS'
Product: [oVirt] ovirt-engine Reporter: mxie <mxie>
Component: BLL.VirtAssignee: Shmuel Melamud <smelamud>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4.1.7CC: ahadas, bugs, juzhou, mzhan, nsimsolo, tyan, tzheng, xiaodwan, zili
Target Milestone: ovirt-4.4.3Flags: pm-rhel: ovirt-4.4+
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: V2V_RHV_INT
Fixed In Version: ovirt-engine-4.4.3.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-11 06:42:18 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:
Attachments:
Description Flags
imported-guest-bios-type.png none

Description mxie@redhat.com 2020-07-30 03:45:47 UTC
Created attachment 1702884 [details]
imported-guest-bios-type.png

Description of problem:
BIOS type of non-uefi guest should be 'cluster default' if the guest is imported on rhv4.4 web and bios type of cluster is 'Q35 Chipset with Legacy BIOS'

Version-Release number of selected component (if applicable):
rhv:4.4.1.8-0.7.el8ev
vdsm-4.40.22-1.el8ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Import guest from VMware on rhv4.4 GUI web:
Open virtual machine option at rhv4.4 web -> click import button -> choose source as VMware ->input ip for vCenter, ESXi, DataCenter, username, password option->click 'Load' button-> select a guest

2.After guest is imported successfully, found the BIOS type of guest is legacy,pls refer to screenshot"imported-guest-bios-type"  


Actual results:
As above description

Expected results:
Because the BIOS type of cluster is 'Q35 Chipset with Legacy BIOS' and BIOS type of non-uefi guest is 'cluster default' If the guest is converted by v2v on standalone v2v server, BIOS type of non-uefi guest should be 'cluster default' as well if the guest is imported on rhv4.4 web 

Additional info:

Comment 1 Shmuel Melamud 2020-08-31 17:33:52 UTC
I couldn't reproduce the bug on the latest master. Most likely it was fixed by https://gerrit.ovirt.org/110500.

Comment 2 Nisim Simsolo 2020-09-13 14:49:11 UTC
Verified:
ovirt-engine-4.4.2.4-0.1.el8ev
vdsm-4.40.26.1-1.el8ev.x86_64
libvirt-daemon-6.0.0-25.2.module+el8.2.1+7722+a9e38cf3.x86_64
qemu-kvm-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.x86_64
virt-v2v-1.40.2-24.module+el8.2.1+7154+47ffd890.x86_64

Verification scenario:
1. Import VM from VMware with EFI BIOS
   Verify imported VM custom chipset is Q35 with UEFI BIOS and custom emulated machine is cluster default.
   Verify imported VM is running successfully.
2. Import VM from VMware with non EFI BIOS
   Verify imported VM custom chipset is cluster default with legacy BIOS and custom emulated machine is cluster default.
   Verify imported VM is running successfully.

Comment 3 Sandro Bonazzola 2020-11-11 06:42:18 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.