Description of problem:
Since we started using qemu-img measure to determine the size of the target volume when copying, the target initial size might be too small depending on the amount of data written, this may lead to forcing extension very quickly which may pause the VM

Patch[1] attempts to alleviate the situation by adding at least 1GB to the initial size, but a better solution would be to use volume_utilization_chunk_mb instead, this value is currently set in vdsm. By moving it to the engine users would no longer need to set it separately on each host and the initial size would correctly match custom sizes that were tested and tuned by users instead of the default 1GB

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
[1] https://gerrit.ovirt.org/c/ovirt-engine/+/111978

[2] https://github.com/oVirt/vdsm/blob/d0d9758197996c636ad328145f9999a7595064a2/lib/vdsm/common/config.py.in#L331