search for: keelan

On Thu, Jun 23, 2016 at 10:57:43AM -0500, libvirt_users@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 > and the image from virt-sparsify does not? (The image testimage1.qcow2 > created with default options). I don't really know what you mean by "full

...if its actually raw? Or is there two way's of doing formatting inside the qcow2 file, one raw and the other called something else? Is there any reason to use raw vs non-raw? From some reading online it appears performance is better with raw files. Is there a downside to using raw? Thanks! Keelan On Fri, 17 Jun 2016 09:11:04 +0100 "Richard W.M. Jones" <rjones@redhat.com> wrote: > On Wed, Jun 15, 2016 at 10:20:54AM -0500, > libvirt_users@skagitattic.com wrote: > > Hello, > > > > I am curious why when using virt-sparsify the apparent-size of the &...

...8:52:35 +0100 "Richard W.M. Jones" <rjones@redhat.com> wrote: > This is incorrect usage. You've told virt-sparsify that the input > image is raw. But it's not raw, it's qcow2. That makes sense, I won't try and tell it the input is raw anymore when its not. Keelan On Thu, 23 Jun 2016 08:52:35 +0100 "Richard W.M. Jones" <rjones@redhat.com> wrote: > On Wed, Jun 22, 2016 at 05:56:09PM -0500, > libvirt_users@skagitattic.com wrote: > > > Delete what you've done and start from the beginning. Describe > > > exactly h...

...backing_file='testimage2.qcow2' encryption=off cluster_size=65536 lazy_refcounts=off # ls -lsh backup-test2.qcow2 196K -rw-r--r-- 1 root root 193K Jun 22 22:48 backup-test2.qcow2 Though perhaps if I actually tried to add them and boot it up something would not work? Keelan On Wed, 22 Jun 2016 09:58:29 +0100 "Richard W.M. Jones" <rjones@redhat.com> wrote: > On Wed, Jun 22, 2016 at 12:40:40AM -0500, > libvirt_users@skagitattic.com wrote: > > So you are saying when I do the virt-sparsify its converting the > > image from raw to [qco...

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 seems to indicate what I would expect where "ls -lh" shows the full apparent size

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 seems to indicate what I would expect where "ls -lh" shows the full apparent size

On Wed, Jun 22, 2016 at 05:56:09PM -0500, libvirt_users@skagitattic.com wrote: > > 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

On Wed, Jun 22, 2016 at 12:40:40AM -0500, libvirt_users@skagitattic.com wrote: > So you are saying when I do the virt-sparsify its converting the image > from raw to [qcow2]? No. virt-sparsify will use the same input and output formats, unless you use the --convert option. > I studied the man page for virt-sparsify and tried again with > the flag "--format raw"