[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Should 'qemu-img commit' sparsify the backing file?
|
From: |
Richard W.M. Jones |
|
Subject: |
Re: [Qemu-devel] Should 'qemu-img commit' sparsify the backing file? |
|
Date: |
Thu, 5 Nov 2015 08:56:22 +0000 |
|
User-agent: |
Mutt/1.5.20 (2009-12-10) |
On Thu, Nov 05, 2015 at 03:14:49PM +0800, Fam Zheng wrote:
> I don't think this the purpose of "qemu-img commit". Committing
> "new" data in overlay.qcow2 has little to do with discarding backing
> image's fragments where there are only explict zeroes.
In that case, why didn't this step sparsify the backing file?
> > (3) Sparsify the overlay:
> >
> > $ virt-sparsify --in-place overlay.qcow2
> > $ du -sh fedora-22.img overlay.qcow2
> > 6.1G fedora-22.img
> > 3.2M overlay.qcow2
> qemu-img convert fedora-22.img fedora-22.img.1
>
> I don't think we have an in-place sparsifier now.
virt-sparsify ...
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top