3.3.2.3. Converting a remote Xen Virtual Machine
Because each disk transfer requires a new SSH session, it is recommended that SSH keys be set up prior to the conversion for authentication. This is especially important for large disks. Otherwise, a user will be required to manually enter SSH credentials for each disk being transferred. Failure to do so before the SSH negotiation times out will cause virt-v2v to fail.
Xen virtual machines can be converted remotely via SSH. Ensure that the host running the virtual machine is accessible via SSH.
To convert the virtual machine, run:
virt-v2v -o rhev -ic xen+ssh://root@vmhost.example.com -os storage.example.com:/exportdomain --network rhevm vm-name
Where vmhost.example.com
is the host running the virtual machine, 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.