Bug 1573462

Summary: wrong SinglePciQxl initialization during import from OVF
Product: [oVirt] ovirt-engine Reporter: Michal Skrivanek <michal.skrivanek>
Component: BLL.VirtAssignee: Arik <ahadas>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: medium Docs Contact:
Priority: high    
Version: 4.2.2CC: bthurber, bugs, michal.skrivanek, nsimsolo, rjones
Target Milestone: ovirt-4.2.4Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: ovirt-engine-4.2.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-26 08:35:05 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:
Bug Depends On:    
Bug Blocks: 910269    

Description Michal Skrivanek 2018-05-01 10:56:55 UTC
https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/utils/src/main/java/org/ovirt/engine/core/utils/ovf/OvfReader.java#L449 causes the single PCI setting to be enabled when there's no SinglePciQxl item in the OVF (oVirt specific). This causes invalid configuration for all Windows guest OSes.

When missing we should initialize it with the OS type default.

Comment 1 Richard W.M. Jones 2018-05-01 11:07:09 UTC
Is any change needed to the OVF that virt-v2v generates?

Comment 2 Richard W.M. Jones 2018-05-01 11:14:43 UTC
I chatted to Michal on IRC and the answer is no.

Comment 3 Nisim Simsolo 2018-06-20 10:22:03 UTC

Verification scenario: 
1. From host CLI shell, use virt-v2v command to import different Windows OS types and Linux OS types to RHV using VDDK input mode (-io vddk).
2. From RHV Webadmin, edit each VM -> console and verify:
Linux VMs: OS type is equal to source VM, single PCI checkbox is not grayed out and checked. 
Windows VMs: OS type is equal to source VM, Single PCI checkbox is grayed out and inaccessible
3. Run each VM and verify VMs are running properly and VM console can be opened.

Comment 4 Sandro Bonazzola 2018-06-26 08:35:05 UTC
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

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