Description of problem: virt-v2v should first check if the export domain is invalid, like if the images/master folder exist, if not ,give error. As now, we need to wait until the v2v generate .ovf file to know like master/vms not exist error, and before that,already finished transfer the image, convert the image,this is unreasonable, and it's time consuming. "aug_match "/files/etc/modules.conf/alias" aug_get "/files/etc/modules.conf/alias" aug_set "/files/etc/modules.conf/alias/modulename" "e1000" aug_save aug_match "/files/boot/grub/menu.lst/title/kernel" aug_get "/files/boot/grub/menu.lst/title/kernel" aug_set "/files/boot/grub/menu.lst/default" "0" aug_get "/files/boot/grub/menu.lst/title[1]/initrd" aug_save exists "/boot/initrd-2.4.21-50.EL.img" mv "/boot/initrd-2.4.21-50.EL.img" "/boot/initrd-2.4.21-50.EL.img.pre-v2v" aug_save modprobe "ext2" modprobe "loop" command "/sbin/mkinitrd --with=sym53c8xx /boot/initrd-2.4.21-50.EL.img 2.4.21-50.EL" command "/sbin/chkconfig kudzu off" umount_all sync umount_all sync kill_subprocess virt-v2v: Failed to create directory /tmp/NACJLJG0xI/d66ccc0c-5fb6-4ac1-bcf8-f0d4e54c2cca/master/vms/42bd32b4-7475-449c-9fe8-4c95bc4d60a1: No such file or directory " Version-Release number of selected component (if applicable): virt-v2v-0.6.0.3 How reproducible: always Steps to Reproduce: 1,create a export domain but didn't attach to any data-center, then it won't create the master folder under the nfs path, 2,run the virt-v2v with the export domain above, Actual results: fail at the last step, saying folder **/master/vms not exist Expected results: check the export domain first to confirm it could be used or not Additional info:
*** Bug 601537 has been marked as a duplicate of this bug. ***
*** Bug 601542 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Posted here: http://www.redhat.com/archives/libguestfs/2010-September/msg00014.html
Verified with virt-v2v-0.6.3-2.el5 1.run virt-v2v -ic xen+ssh://10.66.72.123 -o rhev -osd 10.66.90.115:/vol/v2vrwu2/esx_export rhel5u4-64b-pv-raw-intel 2. virt-v2v: 10.66.90.115:/vol/v2vrwu2/esx_export has not been attached to a RHEV data center (0e6d0cbb-0fa9-438b-a812-cbe24021a2c7/master/vms does not exist) Verified is passed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously, virt-v2v failed at the end of the conversion process when writing to a Red Hat Enterprise Virtualization export domain which had not been attached to a Data Center. This update checks for this and fails at the beginning of the conversion process.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0147.html