RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1134251 - Opening an obviously truncated VMDK image should fail
Summary: Opening an obviously truncated VMDK image should fail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Fam Zheng
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-27 07:58 UTC by Fam Zheng
Modified: 2015-03-05 08:11 UTC (History)
9 users (show)

Fixed In Version: qemu-kvm-1.5.3-84.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 08:11:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0349 0 normal SHIPPED_LIVE Important: qemu-kvm security, bug fix, and enhancement update 2015-03-05 12:27:34 UTC

Description Fam Zheng 2014-08-27 07:58:16 UTC 
For those VMDK images that are even smaller than the value in header field "overhead", the files are obviously truncated and unusable.

We can detect and error out this case:

$ qemu-img create -f vmdk a.vmdk 4T
Formatting 'a.vmdk', fmt=vmdk size=4398046511104 compat6=off zeroed_grain=off

$ truncate a.vmdk --size 1M

Current result:

$ ~/build/rhel7/qemu-img info a.vmdk
image: a.vmdk
file format: vmdk
virtual size: 4.0T (4398046511104 bytes)
disk size: 520K
Format specific information:
    cid: 1409125474
    parent cid: 4294967295
    create type: monolithicSparse
    extents:
        [0]:
            virtual size: 4398046511104
            filename: a.vmdk
            cluster size: 65536
            format:

Expected result:

$ qemu-img info a.vmdk
qemu-img: Could not open 'a.vmdk': File truncated, expecting at least 537985024 bytes
Comment 4 Jeff Nelson 2014-12-16 23:40:40 UTC 
Fix included in qemu-kvm-1.5.3-84.el7
Comment 6 Sibiao Luo 2014-12-24 06:30:31 UTC 
Reproduce this issue:
host info:
# uname -r && rpm -q qemu-kvm
3.10.0-219.el7.x86_64
qemu-kvm-1.5.3-83.el7.x86_64

# qemu-img create -f vmdk a.vmdk 4T
Formatting 'a.vmdk', fmt=vmdk size=4398046511104 compat6=off zeroed_grain=off 
# truncate a.vmdk --size 1M
# qemu-img info a.vmdk
image: a.vmdk
file format: vmdk
virtual size: 4.0T (4398046511104 bytes)
disk size: 520K
Format specific information:
    cid: 1419402502
    parent cid: 4294967295
    create type: monolithicSparse
    extents:
        [0]:
            virtual size: 4398046511104
            filename: a.vmdk
            cluster size: 65536
            format: 

Verify this issue:
host info:
# uname -r && rpm -q qemu-kvm
3.10.0-219.el7.x86_64
qemu-kvm-1.5.3-84.el7.x86_64

# qemu-img create -f vmdk a.vmdk 4T
Formatting 'a.vmdk', fmt=vmdk size=4398046511104 compat6=off zeroed_grain=off 
# truncate a.vmdk --size 1M
# qemu-img info a.vmdk
qemu-img: Could not open 'a.vmdk': File truncated, expecting at least 537985024 bytes

Base on above, this issue has been fixed correctly, move to VERIFIED status, please correct me if any mistake, thanks.

Best Regards,
sluo
Comment 7 Sibiao Luo 2014-12-24 08:46:56 UTC 
Tried the qemu-kvm-rhev-2.1.2-17.el7.x86_64 which also did not have such issue.
host info:
# uname -r && rpm -q qemu-kvm-rhev
3.10.0-219.el7.x86_64
qemu-kvm-rhev-2.1.2-17.el7.x86_64

# qemu-img create -f vmdk a.vmdk 4T
Formatting 'a.vmdk', fmt=vmdk size=4398046511104 compat6=off 
# truncate a.vmdk --size 1M
# qemu-img info a.vmdk
qemu-img: Could not open 'a.vmdk': File truncated, expecting at least 537985024 bytes

Best Regards,
sluo
Comment 9 errata-xmlrpc 2015-03-05 08:11:25 UTC 
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.

https://rhn.redhat.com/errata/RHSA-2015-0349.html
Note You need to log in before you can comment on or make changes to this bug.