On Tue, May 17, 2016 at 06:03:16PM +0300, Yaniv Kaul wrote:
I expect the input images virt-builder uses (by default) to have
preallocation=metadata.
The default images we supply on
http://libguestfs.org are raw sparse.
However maybe you've got your own templates, in which case you can
control the format and preallocation as you like.
However it's still possible that virt-builder might "lose" the
preallocation mode when it performs the steps in the plan (although I
can't at the moment see any case where this would really happen if you
start with qcow2 templates and ask for qcow2 output format). The only
way I can see to deal with this reliably is to model it in the planner
tags + transitions function.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v