Bug 1007708
| Summary: | [RFE] Enable qemu-img to support VMDK version 3 | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Sibiao Luo <sluo> | |
| Component: | qemu-kvm | Assignee: | Fam Zheng <famz> | |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 6.5 | CC: | bsarathy, ederevea, erich, famz, jraju, juzhang, mgalgoci, michen, mkenneth, mrezanin, qzhang, rbalakri, sluo, sputhenp, vanhoof, van.zantvoort, virt-maint | |
| Target Milestone: | rc | Keywords: | FutureFeature | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | qemu-kvm-0.12.1.2-2.420.el6 | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1007710 1090783 1092940 1092941 (view as bug list) | Environment: | ||
| Last Closed: | 2014-10-14 06:51:07 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1007710, 1090783, 1092940, 1092941 | |||
|
Description
Sibiao Luo
2013-09-13 07:49:47 UTC
*** Bug 1029852 has been marked as a duplicate of this bug. *** Yes. There is only a tip about backup software supporting VMDK v3 from VMware: http://kb.vmware.com/kb/2064959 Upstream does support reading, and we are working on backporting this to RHEL. Thank you for updating this. Read capability should be enough for V2V migrations - we just read the VMDK and convert it to QCOW2/RAW/etc. What about 2TB+ volumes? I assume there is no documentation on this and no upstream support. *** Bug 1029852 has been marked as a duplicate of this bug. *** (In reply to Evgheni Dereveanchin from comment #8) > What > about 2TB+ volumes? I assume there is no documentation on this and no > upstream support. The sparse formats should work just well, but there may be some bugs with a big flat, do you have a specific case that's not working? If so feel free to file a bug. Fam Fix included in qemu-kvm-0.12.1.2-2.420.el6 Verify this issue with vSphere client(Version 5.1.0) on qemu-kvm-rhev-0.12.1.2-2.424.el6.x86_64.
host info:
# uname -r && rpm -q qemu-kvm-rhev
2.6.32-448.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.424.el6.x86_64
Steps and results:
1.Install a image in ESXi host, export it into a vmdk v3 image with vSphere client(Version 5.1.0) and then copy it out in localhost.
# qemu-img info sluo-rhel6.5-64bit-vsphere5.1.0-disk1.vmdk
image: sluo-rhel6.5-64bit-vsphere5.1.0-disk1.vmdk
file format: vmdk
virtual size: 10G (10737418240 bytes)
disk size: 2.0G
2.# qemu-img convert -p -f vmdk sluo-rhel6.5-64bit-vsphere5.1.0-disk1.vmdk -O qcow2 sluo-rhel6.5-64bit-vsphere5.1.0-disk1.qcow2
(100.00/100%)
# qemu-img info sluo-rhel6.5-64bit-vsphere5.1.0-disk1.qcow2
image: sluo-rhel6.5-64bit-vsphere5.1.0-disk1.qcow2
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 4.9G
cluster_size: 65536
3.# qemu-img convert -p -f vmdk sluo-rhel6.5-64bit-vsphere5.1.0-disk1.vmdk -O raw sluo-rhel6.5-64bit-vsphere5.1.0-disk1.raw
(100.00/100%)
# qemu-img info sluo-rhel6.5-64bit-vsphere5.1.0-disk1.raw
image: sluo-rhel6.5-64bit-vsphere5.1.0-disk1.raw
file format: raw
virtual size: 10G (10737418240 bytes)
disk size: 4.8G
Base on above, this issue has been fixed correctly, move to VERIFIED status.
Best Regards,
sluo
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1490.html |