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 1029271 - Format specific information (create type) was wrong when create it specified subformat='streamOptimized'
Summary: Format specific information (create type) was wrong when create it specified ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Fam Zheng
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-12 03:03 UTC by Sibiao Luo
Modified: 2015-03-05 08:02 UTC (History)
10 users (show)

Fixed In Version: qemu-kvm-1.5.3-67.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 08:02:12 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 Sibiao Luo 2013-11-12 03:03:12 UTC 
Description of problem:
Tried to create a vmdk image specified subformat='streamOptimized', but format specific information (create type) was wrong when use qemu-img to read it.
BTW, tried other different vmdk create type that did not meet such issue.

Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm
3.10.0-48.el7.x86_64
qemu-kvm-1.5.3-19.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.tried to create a vmdk image specified subformat='streamOptimized'.
# qemu-img create -f vmdk VMDK-data-disk.vmdk -o subformat=streamOptimized 2G
Formatting 'VMDK-data-disk.vmdk', fmt=vmdk size=2147483648 compat6=off subformat='streamOptimized' zeroed_grain=off 
2.use qemu-img to read it.
# qemu-img info VMDK-data-disk.vmdk 
image: VMDK-data-disk.vmdk
file format: vmdk
virtual size: 2.0G (2147483648 bytes)
disk size: 12K
Format specific information:
    cid: 1384223178
    parent cid: 4294967295
    create type: monolithicSparse     <----------------here wrong
    extents:
        [0]:
            compressed: true
            virtual size: 2147483648
            filename: VMDK-data-disk.vmdk
            cluster size: 65536
            format: 

Actual results:


Expected results:
the create type should be 'streamOptimized' as specified when created it.

Additional info:
Comment 1 Fam Zheng 2014-01-23 07:13:33 UTC 
Posted the fix to upstream:

[PATCH] vmdk: Fix format specific information (create type) for streamOptimized
Comment 4 Jeff Nelson 2014-08-08 16:55:01 UTC 
Fix included in qemu-kvm-1.5.3-67.el7
Comment 6 Sibiao Luo 2014-08-28 07:42:25 UTC 
verify this issue.

host info:
# uname -r && rpm -q qemu-kvm
3.10.0-145.el7.x86_64
qemu-kvm-1.5.3-67.el7.x86_64

[root@dhcp-11-154 home]# qemu-img create -f vmdk VMDK-data-disk.vmdk -o subformat=streamOptimized 2G
Formatting 'VMDK-data-disk.vmdk', fmt=vmdk size=2147483648 compat6=off subformat='streamOptimized' zeroed_grain=off 
[root@dhcp-11-154 home]# qemu-img info VMDK-data-disk.vmdk
image: VMDK-data-disk.vmdk
file format: vmdk
virtual size: 2.0G (2147483648 bytes)
disk size: 12K
Format specific information:
    cid: 1409211551
    parent cid: 4294967295
    create type: streamOptimized
    extents:
        [0]:
            compressed: true
            virtual size: 2147483648
            filename: VMDK-data-disk.vmdk
            cluster size: 65536
            format: 

Base on above, this issue has been fixed correctly, move to VERIFIED status.

Best Regards,
sluo
Comment 7 Sibiao Luo 2014-09-01 08:10:46 UTC 
Comment #6 was on Intel host.

Now i tried the qemu-kvm-rhev on AMD host.
host info:
# uname -r && rpm -q qemu-kvm-rhev
3.10.0-147.el7.x86_64
qemu-kvm-rhev-2.1.0-2.el7.x86_64

Results:
# qemu-img create -f vmdk VMDK-data-disk.vmdk -o subformat=streamOptimized 2G
Formatting 'VMDK-data-disk.vmdk', fmt=vmdk size=2147483648 compat6=off subformat='streamOptimized' 
# qemu-img info VMDK-data-disk.vmdk
image: VMDK-data-disk.vmdk
file format: vmdk
virtual size: 2.0G (2147483648 bytes)
disk size: 12K
cluster_size: 65536
Format specific information:
    cid: 1409558382
    parent cid: 4294967295
    create type: streamOptimized
    extents:
        [0]:
            compressed: true
            virtual size: 2147483648
            filename: VMDK-data-disk.vmdk
            cluster size: 65536
            format: 

Best Regards,
sluo
Comment 8 Sibiao Luo 2014-09-01 08:11:24 UTC 
According to comment #6 and comment #7, this issue has been fixed correctly, move to VERIFIED status.

Best Regards,
sluo
Comment 10 errata-xmlrpc 2015-03-05 08:02:12 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.