Why does virt-v2v fail while converting a virtual machine from a Xen/VMware ESX Host to RHEV?

Solution Verified - Updated -


  • Red Hat Enterprise Virtualization 3.0
  • virt-v2v
  • Red Hat Enterprise Linux
  • VMWare ESX or Xen


  • virt-v2v fails when trying to convert a vm running on XEN/VMware ESX Host
  • Error message for example:
[root@rhevm ~]# virt-v2v -ic esx:// -o rhev -os --network rhevm abrucena_clone
guestfs_launch failed, see earlier error messages at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 96. <===


  • This issue might occur if guest is running on XEN/VMware ESX Host with four attached disks. Migrating guest with four attached disk is not supported. Remove any of the disk from guest and then try migrating with same procedure.

  • If the user uses Raw Device Mapping device on ESX,the user detached it and attached it to RHEV.It does
    not need convert.

  • This is currently opened as RHBZ #981739

Diagnostic Steps

  • Check number of attached disks to the guest.
  • Run below commands from the conversion server:
 # export LIBVIRT_DEBUG=1
 # virt-v2v -o rhev -os slmaq010.maif.local:/data_tech/virtual_machines/export_domain --network rhevm slmaq030 2>&1 | tee virt-v2v.log

and provide virt-v2v.log

Note: Run above commands in the same order mentioned above.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.