Questo contenuto non è disponibile nella lingua selezionata.
4.3.2.5. Converting a remote KVM virtual machine
KVM virtual machines can be converted remotely via SSH. Ensure that the host running the virtual machine is accessible via SSH, and that the virtual machine is stopped prior to running the v2v process. Even on a guest with multiple disks, each virtual disk transfer requires a separate SSH session.
Important
It is recommended to set up SSH keys for authentication prior to the remote virtual machine conversion. Otherwise, a user will be required to manually enter SSH credentials for each guest disk being transferred. Failure to enter a password manually in the time after the transfer completes but before the SSH negotiation times out will cause
virt-v2v to fail. This is especially important for large disks, as the disk transfer can take an unspecified length of time.
To convert the virtual machine, run:
virt-v2v -ic qemu+ssh://root@kvmhost.example.com/system -o rhev -os storage.example.com:/exportdomain --network rhevm guest_name
virt-v2v -ic qemu+ssh://root@kvmhost.example.com/system -o rhev -os storage.example.com:/exportdomain --network rhevm guest_name
Where
kvmhost.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 guest_name is the name of the KVM virtual machine.
You may also use the
--bridge 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.