On 21.02.2013 06:27, Chen Hanxiao wrote: > From: Chen Hanxiao <chenhanxiao@xxxxxxxxxxxxxx> > > As discussed in: > https://www.redhat.com/archives/virt-tools-list/2013-February/msg00154.html > There is a bug when creating disk image as qcow2, enable > fully allocating but get the minimal sparse image. > > We should give users a notification which describing this. > > Signed-off-by: Chen Hanxiao <chenhanxiao@xxxxxxxxxxxxxx> > --- > src/virtManager/uihelpers.py | 4 +++- > 1 files changed, 3 insertions(+), 1 deletions(-) > > diff --git a/src/virtManager/uihelpers.py b/src/virtManager/uihelpers.py > index 13cc4c1..6267219 100644 > --- a/src/virtManager/uihelpers.py > +++ b/src/virtManager/uihelpers.py > @@ -72,7 +72,9 @@ def set_sparse_tooltip(widget): > "but the OS install phase will be quicker. \n\n" > "Skipping allocation can also cause space issues on " > "the host machine, if the maximum image size exceeds " > - "available storage space.") > + "available storage space. \n\n" > + "Tip: Storage format qcow2 and qed " > + "could not support full allocation.") > util.tooltip_wrapper(widget, sparse_str) > > def host_disk_space(conn): > Even though, this is not virt-manager bug (the buck passes through virt-install and libvirt to qemu-img which cannot be told how much to allocate - and I am not speaking about sparse files here), I guess it won't be solved in near future. So until then, we should warn. Michal _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
