On Thu, 23 Jun 2016 17:57:53 +0100
"Richard W.M. Jones" wrote:
> On Thu, Jun 23, 2016 at 10:57:43AM -0500,
> libvirt_us...@skagitattic.com wrote:
> > Thanks for all the information, I think my last remaining question
> > is why the image created with virt-install shows the full apparent
> > size
Hello,
Thanks for all the information, I think my last remaining question is
why the image created with virt-install shows the full apparent size
and the image from virt-sparsify does not? (The image testimage1.qcow2
created with default options).
As they are both qcow2 I would expect them both
> Delete what you've done and start from the beginning. Describe
> exactly how you created the guest. Use 'qemu-img info' to show the
> format of the input file. Show precisely the virt-sparsify command
> you are running. And use 'qemu-img info' on the output file too.
Okay, here goes. Star
Hello Rich,
Thanks for the reply and information.
> What is file.img?
Its simply a file I made while testing sparse files "truncate -s 512M
file.img".
> 'du --apparent-size' and 'ls -l' are the same thing, so it's not
> really surprising that you see the same numbers here.
Indeed, I expected t
Hello,
I am curious why when using virt-sparsify the apparent-size of the file
gets reduced to the actual file size? Is there a way to get the
apparent-size left as the full size?
In the man page for virt-sparsify it has a section on
"IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES" and its output se
