Bug 1415820

Summary: [RFE] Add support to qemu-img for resizing with preallocation
Product: Red Hat Enterprise Linux 7 Reporter: Ademar Reis <areis>
Component: qemu-kvm-rhevAssignee: Hanna Czenczek <hreitz>
Status: CLOSED DUPLICATE QA Contact: Ping Li <pingl>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: aliang, chayang, coli, dchaplyg, hachen, hhuang, hreitz, juzhang, michen, ngu, pingl, qzhang, rbalakri, shuang, virt-maint, xuma, xuwei
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1414049 Environment:
Last Closed: 2017-05-22 21:24:15 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: 1414049, 1475978    
Bug Blocks:    

Description Ademar Reis 2017-01-23 19:50:24 UTC
+++ This bug was initially created as a clone of Bug #1414049 +++

Description of problem:
At the moment qemu-img allows you to specify how image file should be allocated during creation, using 'preallocation' option. Onr of possible choices is using 'falloc' option to fully allocate image file using fallocate(2) call.

Unfortunately, resize operation only supports sparse resizing and there is no way to preallocate new disk space during resize operation. 

It would be nice, if qemu-img will support preallocation during resize with fallocate(2) and, possibly, some fallback preallocation method.

Comment 1 Ping Li 2017-03-14 10:03:02 UTC
Hi Max,

As the flag rhel-7.4.0? is set, qe wonder to know whether the issue will be fixed in rhel 7.4? Then qe can add it to RHEL 7.4 test plan for disk format. Thanks.

Comment 2 Hanna Czenczek 2017-03-15 22:40:29 UTC
Hi pingl,

I'm most certainly working on getting it into 7.4. Considering that the development phase ends on March 28 and upstream qemu is currently occupied with preparing the 2.9 release, it may very well slip to 7.5, however.
So I cannot give a definite response but if I had to decide I would guess it won't make it into 7.4 (since it's an RFE).


Max