Description of problem:
When cold migrating raw-preallocated file-based disk to a different file-based storage domain, the new disk create as RAW-Sparse instead of RAW-Preallocated.
After migrating the disk, it presented as "thin-provisioned" disk instead of "preallocated" and the disk actual size not equal to its provisional size (using qemu-img info).
There are two reasons for this bug:
1. The engine instructs the VDSM to create the raw-preallocated file-based disk as "sparse".
2. The vdsm use 'qemu-img convert' without the preallocation option (FALLOC).
Version-Release number of selected component (if applicable):
master-4.3.0 - from commit dd5c57f39e9ba031ae7abb734c33ee89965cc21c
Steps to Reproduce:
1. Create 2 GB raw-preallocated file-based disk
2. Migrate the disk from step 1 to different file-based disk
The disk becomes "thin-provisioned"
The disk should remain as "preallocated"
Relevant also when migrating preallocated block-based disk to file storage domain
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Verified on engine 188.8.131.52-0.1.
This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019.
Since the problem described in this bug report should be
resolved in oVirt 4.3.3 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.