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

Bug 1437064

Summary: [Docs][VMM] Document the need to configure the CPU for VMs imported from an external provider
Product: Red Hat Enterprise Virtualization Manager Reporter: Tomas Jelinek <tjelinek>
Component: DocumentationAssignee: Avital Pinnick <apinnick>
Status: CLOSED CURRENTRELEASE QA Contact: Emma Heftman <eheftman>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.1.0CC: adahms, lbopf, lsurette, rbalakri, srevivo, tjelinek, ykaul, ylavi
Target Milestone: ovirt-4.1.6   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-30 11:50:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Jelinek 2017-03-29 13:00:24 UTC
A known limitation needs to be added to the import of virtual machines from external provider (e.g. vmware) explaining that:

If the CPU of the VM before import is different than the one configured in the ovirt cluster (edit cluster->general->cpu type) than the VM's custom CPU type has to be configured after import to match the VM's CPU (in edit VM -> system -> Advanced Parameters -> Custom CPU Type).

We can not do it automatically so far and the support on libguestfs layer is far away [1], so needs to be documented as a known limitation.

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1432329

Comment 1 Lucy Bopf 2017-08-08 07:40:50 UTC
Assigning to Avital for review.

Comment 3 Tomas Jelinek 2017-08-10 07:22:09 UTC
thank you, loogs good

Comment 5 Emma Heftman 2017-08-30 10:07:38 UTC
Verified and merged.