Red Hat Bugzilla – Bug 714159
[RFE] virt-v2v support for import of standalone virtual machine into RHEV export domain
Last modified: 2014-11-18 06:20:00 EST
Description of problem:
This is an RFE to support import of standalone virtual machine into a RHEV export domain. Currently, the only supported methods are from a running hypervisor. Often, users of RHEV may only be provided an exported virtual machine image on media (USB HDD, DVD, etc) and would like to import this into a RHEV environment.
The following command should be supported:
virt-v2v -i libvirtxml -o rhev -os 18.104.22.168:/exportdomain filename-libvirt.xml
Depends on qemu VMDK support being fixed (bug 548723).
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Any idea when this will be resolved? The issue seems quite inactive, but at least for us it is still clearly a desired feature.
You can follow development upstream on the mailing list, eg
latest thread from today:
and in the git repository. See http://libguestfs.org/ for more links.
Virt-v2v needs to run on the latest Red Hat Enterprise Linux release
to ensure it can correctly read and modify new guest filesystem
features. A new version of virt-v2v is now available for RHEL 7.1.
Before RHEL 7.1 is released, follow the instructions here to
install unsupported preview packages on top of RHEL 7.0:
After RHEL 7.1 is released, virt-v2v will be available in
You can run virt-v2v in a single virtual machine. Other
requirements are covered here:
If you find a missing feature or bug in the new version of virt-v2v
please file a bug using the following link: