Once you have the images converted to raw disk images and a libvirt.xml file we can virt-v2v to import them into RHEVM. # qemu-img convert test.vmdk -O raw test.img If you do not have the meta data you can manually convert the disk file, vmdk, using qemu-img, then manually create your own libvirt.xml file: It should convert the image, assuming the vmdk file is is the same dir. If you have the meta data exported form VMware as either an ovf file or vmx file you can run virt-convert directly on the meta data file. You have to either have the meta data, xml file, exported form the VMware server, or create you own libvirt.xml file to pass to virt-v2v.The VMware exported images are exported as FLAT images, not compressed images.However this will only work under the following conditions. There is some work being done at Google Summer of Code to address this, however not complete.įrom what I can tell you can do the conversions manually by first using virt-convert to convert the VMware images into libvirt images, then use virt-v2v to import them into RHEV. Specifically, The qemu-img vmdk block driver can't handle VMware4 compressed images. It looks like there is already an open RFE for virt-v2v to work on stand-alone VMDK files, however there are a couple blocking issues.
