3.3.2.2. Converting a local Xen Virtual Machine
Ensure that the 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 -o rhev -os storage.example.com:/exportdomain --network rhevm vm-name.xml
Where storage.example.com:/exportdomain
is the export storage domain, rhevm
is the locally managed network to connect the converted virtual machine's network to, and vm-name.xml
is the path to the virtual machine's exported xml. You may also use the --bridge
parameter to connect to a local network bridge, or specify multiple mappings in /etc/virt-v2v.conf
.
To convert the virtual machine from a running Xen hypervisor, run:
virt-v2v -ic xen:/// -o rhev -os storage.example.com:/exportdomain --network rhevm vm-name
Where storage.example.com:/exportdomain
is the export storage domain, rhevm
is the locally managed network to connect the converted virtual machine's network to, and vm-name
is the domain of the Xen virtual machine. You may also use the --bridge
parameter to connect to a local network bridge, or specify multiple mappings in /etc/virt-v2v.conf
.
If your guest uses a Xen para-virtualized 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 won't 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.