| Summary: | Failed to create new volume while converting guest to RHEV | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Qin Guan <qguan> |
| Component: | virt-v2v | Assignee: | Matthew Booth <mbooth> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.7 | CC: | cshao, leiwang, mbooth, mkenneth, rjones, rwu, sgordon, whuang, yupzhang |
| Target Milestone: | rc | Keywords: | Regression, Reopened, TestBlocker |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | virt-v2v-0.7.1-3.el5 | Doc Type: | Bug Fix |
| Doc Text: |
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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-08-05 17:39:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Qin Guan
2011-04-14 09:48:31 UTC
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
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 |