3.3.3. Converting a local Xen virtual machine

Ensure that the guest virtual machine's XML is available locally, and that the storage referred to in the XML is available locally at the same paths.
To convert the virtual machine from an XML file, run:
virt-v2v -i libvirtxml -op pool --bridge bridge_name guest_name.xml
Where pool is the local storage pool to hold the image, bridge_name is the name of a local network bridge to connect the converted virtual machine's network to, and guest_name.xml is the path to the virtual machine's exported XML.
You may also use the --network parameter to connect to a locally managed network if your virtual machine only has a single network interface. If your virtual machine has multiple network interfaces, edit /etc/virt-v2v.conf to specify the network mapping for all interfaces.
If your virtual machine uses a Xen paravirtualized kernel (it would be called something like kernel-xen or kernel-xenU), virt-v2v will attempt to install a new kernel during the conversion process. You can avoid this requirement by installing a regular kernel, which will not reference a hypervisor in its name, alongside the Xen kernel prior to conversion. You should not make this newly installed kernel your default kernel, because Xen will not boot it. virt-v2v will make it the default during conversion.

Note

When converting from Xen, virt-v2v requires that the image of the source virtual machine exists in a storage pool. If the image is not currently in a storage pool, you must create one. Contact Red Hat Support for assistance creating an appropriate storage pool.

Note

Presently, there is a known issue with importing Citrix Xen virtual machines to run on KVM or Red Hat Enterprise Virtualization. For more information, see https://access.redhat.com/solutions/54076.