Bug 1415582

Summary: [Docs][RFE][VMM] virt-v2v from RHEL Xen: Document virt-v2v workaround for converting VM with block device
Product: Red Hat Enterprise Virtualization Manager Reporter: Tahlia Richardson <trichard>
Component: DocumentationAssignee: Avital Pinnick <apinnick>
Status: CLOSED CURRENTRELEASE QA Contact: Tahlia Richardson <trichard>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.1.0CC: lbopf, lsurette, nsimsolo, rbalakri, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.1.3Keywords: FutureFeature
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-22 07:37:56 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:
Bug Depends On: 1375563    
Bug Blocks:    

Description Tahlia Richardson 2017-01-23 06:45:59 UTC
Currently, virtual machines with block devices cannot be imported from Xen to Red Hat Virtualization using the Administration Portal. This release adds a workaround to manually import Xen virtual machines with block devices: 

1. Create an export domain.
2. Run the following command to copy the files locally:
   $ virt-v2v-copy-to-local -ic xen+ssh://root vmname
3. Run the following command to convert the virtual machine to libvirt XML:
   $ virt-v2v -i libvirtxml vmname.xml -o rhev -of raw -os servername:/path/to/export/domain
4. The virtual machine should now appear in your export domain, and can be imported to a data domain.

A note or procedure with these steps should be added in or near the existing Importing a Virtual Machine from a Xen Host section.

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