Bug 1480221 - [Docs][VMM] Correct procedure "Importing a Virtual Machine from a Xen Host"
[Docs][VMM] Correct procedure "Importing a Virtual Machine from a Xen Host"
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: ovirt-4.1.6
: ---
Assigned To: Megan Lewis
Depends On:
  Show dependency treegraph
Reported: 2017-08-10 08:27 EDT by Avital Pinnick
Modified: 2017-09-28 04:49 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Docs
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Avital Pinnick 2017-08-10 08:27:39 EDT
Nisim Simsolo wrote:

- "13. Select the Collapse Snapshots check box to remove snapshot restore points and include templates in template-based virtual machines." 
    Is not relevant (not part of second import dialog page.)
- "15. Click on each virtual machine to be imported and click on the Disks sub-tab. Use the Allocation Policy and Storage Domain lists to select whether the disk used by the virtual machine will be thinly provisioned or preallocated, and select the storage domain on which the disk will be stored. An icon is also displayed to indicate which of the disks to be imported acts as the boot disk for that virtual machine. "
    Not relevant to the second import dialog page.
- "16. If you selected the Clone check box, change the name of the virtual machine in the General sub-tab."
    Changing VM name when selecting clone is not "must to do", it depends if there's a VM with the same name in RHV VMs. It's possible to import VM as clone and keep the source vM name. if there's a VM with the same name in RHV VMs, an error pop-up message will appear mentioning that VM Name already exist in the Data Center.
- It would be nice to have a note mentioning that virtio drivers should be attached when importing Windows VMs in order to install them during conversion.

Note You need to log in before you can comment on or make changes to this bug.