I think this was fixed in libvirt upstream, please reopen and correct me if I'm wrong
commit 81a3042a12c7c06adc8e95264b6143b2eeb4953f
Author: Pavel Hrdina <email address hidden>
Date: Tue Aug 25 15:09:53 2020 +0200
storage_util: fix qemu-img sparse allocation
Commit <c9ec7088c7a3f4cd26bb471f1f243931fff6f4f9> introduced a support
to fully allocate qcow2 images when <allocation> matches <capacity> but
it doesn't work as expected.
The issue is that info.size_arg is in KB but the info.allocation
introduced by the mentioned commit is in B. This results in using
"preallocation=falloc," in cases where "preallocation=metadata," should
be used.
Signed-off-by: Pavel Hrdina <email address hidden>
Reviewed-by: Michal Privoznik <email address hidden>
I think this was fixed in libvirt upstream, please reopen and correct me if I'm wrong
commit 81a3042a12c7c06 adc8e95264b6143 b2eeb4953f
Author: Pavel Hrdina <email address hidden>
Date: Tue Aug 25 15:09:53 2020 +0200
storage_util: fix qemu-img sparse allocation
Commit <c9ec7088c7a3f4 cd26bb471f1f243 931fff6f4f9> introduced a support
to fully allocate qcow2 images when <allocation> matches <capacity> but
it doesn't work as expected.
The issue is that info.size_arg is in KB but the info.allocation ion=falloc, " in cases where "preallocation= metadata, " should
introduced by the mentioned commit is in B. This results in using
"preallocat
be used.
Signed-off-by: Pavel Hrdina <email address hidden>
Reviewed-by: Michal Privoznik <email address hidden>