Installation guide

Converting a local Xen virtualized guest
177
--version Display version number and exit.
23.2.2. Converting a local Xen virtualized guest
Ensure that the virtualized guest's XML is available locally, and that the storage referred to in the XML
is available locally at the same paths.
To convert the virtualized guest from an XML file, run:
virt-v2v -i libvirtxml -op pool --bridge brname vm-name.xml
Where pool is the local storage pool to hold the image, brname is the name of a local network bridge
to connect the converted guest's network to, and vm-name.xml is the path to the virtualized guest's
exported XML. You may also use the --network parameter to connect to a locally managed network,
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.
23.2.3. Converting a remote Xen virtualized guest
Xen virtualized guests can be converted remotely via SSH. Ensure that the host running the virtualized
guest is accessible via SSH.
To convert the virtualized guest, run:
virt-v2v -ic xen+ssh://[e-mail] -op pool --bridge brname vm-name
Where vmhost.example.com is the host running the virtualized guest, pool is the local storage
pool to hold the image, brname is the name of a local network bridge to connect the converted
guest's network to, and vm-name is the domain of the Xen virtualized guest. You may also use the --
network parameter to connect to a locally managed network, 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.
23.2.4. Converting a VMware ESX virtualized guest
Ensure that the virtualized guest is stopped prior to running the v2v process.
To convert the virtualized guest, run:
virt-v2v -ic esx://esx.example.com/ -op pool --bridge brname vm-name
Where esx.example.com is the VMware ESX server, pool is the local storage pool to hold the
image, brname is the name of a local network bridge to connect the converted guest's network to,
and vm-name is the name of the virtualized guest. You may also use the --network parameter to
connect to a locally managed network, or specify multiple mappings in /etc/virt-v2v.conf.