Troubleshooting virt-v2v related issues
Here are a few points to keep in mind while troubleshooting virt-v2v:
- Ensure that the required v2v packages are installed on the virt-v2v conversion server. For example, libguestfs-winsupport and virtio-win are installed when a Windows guest migration is planned.
- Ensure that SSH is enabled on the source host machine.
- Make sure that the Export Storage domain has enough space to accommodate new virtual machines.
- Verify that the virt-v2v command syntax that is being used is correct. The virt-v2v man page has a detailed explanation of each parameter and examples are also included.
Everything fine, but the migration is still failing?
In such a situation, enabling virt-v2v debug logs will be helpful. Virt-v2v debug logs can be enabled by prefixing the virt-v2v command with the following environment variables:
LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1
The following is what the command will look like:
#LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1 virt-v2v -icxen+ssh://root@vmhost...
