Bug 1573462
Summary: | wrong SinglePciQxl initialization during import from OVF | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Michal Skrivanek <michal.skrivanek> |
Component: | BLL.Virt | Assignee: | Arik <ahadas> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.2.2 | CC: | bthurber, bugs, michal.skrivanek, nsimsolo, rjones |
Target Milestone: | ovirt-4.2.4 | Flags: | rule-engine:
ovirt-4.2+
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 910269 |
Description
Michal Skrivanek
2018-05-01 10:56:55 UTC
Is any change needed to the OVF that virt-v2v generates? I chatted to Michal on IRC and the answer is no. Verified: ovirt-engine-4.2.4.2-0.1.el7_3 vdsm-4.20.29-1.el7ev.x86_64 libvirt-client-3.9.0-14.el7_5.6.x86_64 qemu-kvm-rhev-2.10.0-21.el7_5.3.x86_64 sanlock-3.6.0-1.el7.x86_64 virt-v2v-1.36.10-6.10.rhvpreview.el7ev.x86_64 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. 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. |