Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1057930 - qemu-img can not create vmdk type monolithicFlat with zeroed_grain=on
Summary: qemu-img can not create vmdk type monolithicFlat with zeroed_grain=on
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Fam Zheng
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-26 03:09 UTC by Qian Guo
Modified: 2014-01-27 05:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-27 05:59:28 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Qian Guo 2014-01-26 03:09:11 UTC
Description of problem:
qemu-img can not create vmdk type monolithicFlat with zeroed_grain=on 

And found that this bug is regression, from qemu-kvm-1.5.3-17.el7.x86_64. (qemu-kvm-1.5.3-15.el7.x86_64 has not such issue.)
Version-Release number of selected component (if applicable):

qemu-kvm-1.5.3-41.el7.x86_64
qemu-img-1.5.3-41.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Try to create vmdk image type monolithicFlat with zeroed_grain=on
# qemu-img create -f vmdk -o subformat=monolithicFlat,zeroed_grain=on VMDK-data-disk.vmdk 2G
2.
3.

Actual results:
# qemu-img create -f vmdk -o subformat=monolithicFlat,zeroed_grain=on VMDK-data-disk.vmdk 2G
Formatting 'VMDK-data-disk.vmdk', fmt=vmdk size=2147483648 compat6=off subformat='monolithicFlat' zeroed_grain=on 
qemu-img: VMDK-data-disk.vmdk: Flat image can't enable zeroed grain

Expected results:
Can create successfully

Additional info:
regression


Note You need to log in before you can comment on or make changes to this bug.