Hide Forgot
Description of problem: Failed to create new volume for over size while converting guest to RHEV. # virt-v2v -ic xen+ssh://10.66.72.123 -n rhevm -o rhev -osd 10.66.8.177:/home/export xen-pv-rhel5.6-i386 root.72.123's password: root.72.123's password: virt-v2v: Failed to create new volume /tmp/FDE4jJTC3l/6bed8854-8800-46c0-9089-6a477e57152f/v2v.olGNXtmO/41d86cc9-5eda-46ef-8395-d10c5068962a/a6385d52-a23a-48da-9c38-e240c05b3116 with format raw. Error was: qemu-img: Error while formatting Formatting '/tmp/FDE4jJTC3l/6bed8854-8800-46c0-9089-6a477e57152f/v2v.olGNXtmO/41d86cc9-5eda-46ef-8395-d10c5068962a/a6385d52-a23a-48da-9c38-e240c05b3116', fmt=raw, size=6442450944 kB The disk size for the guest is 6442450944 bytes, while qemu-img on RHEL5.7 uses kB to create the image and then failed. Version-Release number of selected component (if applicable): kernel:2.6.18-256.el5 virt-v2v-0.7.1-2.el5 libguestfs-1.2.7-1.el5.13 libvirt-0.8.2-15.el5_6.3 How reproducible: 100% Steps to Reproduce: 1.create a nfs_export on local disk 2.change the nfs_export directory to 36:36 permission 3.create and attach the storage to RHEV-M 4.convert a guest into the RHEV Actual results: Failed to create new volume while converting Expected results: Convert successfully Additional info:
No such problem on 5.6 (virt-v2v-0.6.3-5.el5).
Verified on virt-v2v with version 0.7.1-4. virt-v2v-0.7.1-4.el5 libvirt-python-0.8.2-18.el5 libvirt-0.8.2-18.el5 perl-libguestfs-1.2.7-1.el5.13 libguestfs-1.2.7-1.el5.13 zlib-1.2.3-3 Convert to rhev sucessfully: # virt-v2v -ic xen+ssh://10.66.72.123 -o rhev -os 10.66.10.160:/tmp/nfs_export xen-hvm-rhel5.7-i386 root.72.123's password: root.72.123's password: virt-v2v: Transferring storage volume xen-hvm-rhel5.7-i386.img: 4194304000 bytes virt-v2v: WARNING: No mapping found for bridge interface virbr0 in config file. The converted guest may not start until its network interface is updated. virt-v2v: xen-hvm-rhel5.7-i386 configured with virtio drivers The disk size is as expected: # ls -lsh /rhev/data-center/mnt/10.66.10.160\:_tmp_nfs__export/b8cc9f96-66e4-401a-8104-c6357eeff91e/images/8c61b190-a9fb-41b8-8e45-ca001e4bb9f7/bba2d69c-e983-4d40-8e38-925d48f4cd7a 4.0G -rw-r--r-- 1 vdsm kvm 4.0G May 26 10:13 /rhev/data-center/mnt/10.66.10.160:_tmp_nfs__export/b8cc9f96-66e4-401a-8104-c6357eeff91e/images/8c61b190-a9fb-41b8-8e45-ca001e4bb9f7/bba2d69c-e983-4d40-8e38-925d48f4cd7a
Set it as VERIFIED according to comment 4.
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: When creating a volume virtv2v provided the disk size in bytes while the qemu-img process expected the disk size in kilobytes. The resultant disk images were significantly larger than expected. Both processes now pass the disk size in kilobytes.
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-1125.html