similar to: IRC question: can virt-sparsify output to stdout instead of a file?

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

On Tue, Oct 13, 2020 at 07:56:29PM +0300, Nir Soffer wrote: > On Tue, Oct 13, 2020 at 7:15 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > On Tue, Oct 13, 2020 at 06:45:42PM +0300, Nir Soffer wrote: > > > I think this is the right solution - when virt-something tool fails, > > > it should log the reason for the failure - the error that caused the

On Wed, Nov 04, 2015 at 01:10:04PM +0200, Yaniv Kaul wrote: > On Wed, Nov 4, 2015 at 12:49 PM, Richard W.M. Jones <rjones@redhat.com> > wrote: > > All that happened was that the overlay got bigger (because it's now > > storing a bunch of qcow2 zero clusters marking the places in the > > backing file which are zero). ^^^ Here I should

[I don't normally monitor this list for issues - it's better to send bugs to the libguestfs mailing list] On Tue, Aug 28, 2012 at 09:07:23PM +0100, Paul Maunders wrote: > I've found an issue with virt-sparsify on Centos 6.3 with it's image > format detection. If I take a qcow2 image and attempt to sparsify it > with... > > virt-sparsify -v centos6.3-gold.img

On Mon, Nov 09, 2020 at 09:16:33AM +0200, Yedidyah Bar David wrote: > On Wed, Oct 14, 2020 at 8:54 AM Yedidyah Bar David <didi@redhat.com> wrote: > > > > On Tue, Oct 13, 2020 at 8:40 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > > > On Tue, Oct 13, 2020 at 07:56:29PM +0300, Nir Soffer wrote: > > > > On Tue, Oct 13, 2020 at 7:15 PM

On Wed, Nov 4, 2015 at 12:49 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > [Let's discuss this upstream] > > On Wed, Nov 04, 2015 at 12:18:48PM +0200, Yaniv Kaul wrote: > > I'm missing something here - what will happen to the tree structure? > > Will we lose it? So essentially it performs a merge? > > In copying mode: > > virt-sparsify disk1

On Wed, May 27, 2020 at 02:44:19PM +0800, P.V.Anthony wrote: > Hi, > > On CentOS 8, when using virt-sparsify for a ntfs image, it does not > seem to work. > > Tried virt-sparsify on Fedora 32 and it works great. > > Is there some dependent application that need to be installed in > CentOS 8 for virt-sparsify to work on ntfs? Which version of libguestfs-winsupport

On Wed, Oct 14, 2020 at 8:54 AM Yedidyah Bar David <didi at redhat.com> wrote: > > On Tue, Oct 13, 2020 at 8:40 PM Richard W.M. Jones <rjones at redhat.com> wrote: > > > > On Tue, Oct 13, 2020 at 07:56:29PM +0300, Nir Soffer wrote: > > > On Tue, Oct 13, 2020 at 7:15 PM Richard W.M. Jones <rjones at redhat.com> wrote: > > > > > > >

On Mon, Oct 12, 2020 at 9:05 AM Yedidyah Bar David <didi@redhat.com> wrote: > > Hi all, > > On Mon, Oct 12, 2020 at 5:17 AM <jenkins@jenkins.phx.ovirt.org> wrote: > > > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ > > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/479/ > >

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 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

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 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

[Let's discuss this upstream] On Wed, Nov 04, 2015 at 12:18:48PM +0200, Yaniv Kaul wrote: > I'm missing something here - what will happen to the tree structure? > Will we lose it? So essentially it performs a merge? In copying mode: virt-sparsify disk1 disk2 creates an overlay on top of disk1, writes zeroes to the overlay in the parts of disk1 which are not used (disk1 is not

Try adding a dummy drive with discard enabled as test before using virt-sparsify --in-place (which needs discard). --- sparsify/test-virt-sparsify-in-place.sh | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/sparsify/test-virt-sparsify-in-place.sh b/sparsify/test-virt-sparsify-in-place.sh index 56311a0..b098c90 100755 --- a/sparsify/test-virt-sparsify-in-place.sh

Since Linux commit f663b5b38fff trimming vfat is now supported by Linux. This broke the test which assumed it was not supported. Use another filesystem (minix) which does not support trimming instead. Thanks: Daniel P. Berrangé and Pino Toscano. --- ...est-virt-sparsify-in-place-fstrim-unsupported.sh | 13 ++++++------- tests/test-functions.sh | 10 ++++++++++ 2

On Tue, Nov 24, 2015 at 02:30:42PM +0200, Yaniv Kaul wrote: > Assuming the VM is not running, and we have a base (raw, sparse) with a > snapshot (qcow2) on top of it. > Is there any issue with running virt-sparsify on the base image? I assume > deleted blocks in the base can be sparsified, since they are either still > deleted on the snap (which is fine) or were written in the snap

On Wed, Jan 27, 2016 at 09:24:47PM +0200, Illia Svyrydov wrote: > Here is *libguestfs-test-tool* output > > http://pastebin.com/raw/anuu6wkh I'm guessing that /tmp (on the host) either doesn't exist, or is a symlink to a directory that doesn't get copied to the appliance, or something along those lines. This was fixed upstream in:

Since Linux commit f663b5b38fff trimming vfat is now supported by Linux. This broke the test which assumed it was not supported. Use another filesystem (minix) which does not support trimming instead. Thanks: Daniel P. Berrangé and Pino Toscano. --- ...virt-sparsify-in-place-fstrim-unsupported.sh | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git

Hi, On CentOS 8, when using virt-sparsify for a ntfs image, it does not seem to work. Tried virt-sparsify on Fedora 32 and it works great. Is there some dependent application that need to be installed in CentOS 8 for virt-sparsify to work on ntfs? Here are some information. CentOS 8. # virt-sparsify -V virt-sparsify 1.38.4rhel=8,release=14.module_el8.1.0+248+298dec18,libvirt #

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

Hi! This question emerged during testing of oVirt sparsify integration. oVirt now is able to run virt-sparsify on VM disks. But virt-sparsify seems to have no effect on iSCSI disks. Does virt-sparsify work on iSCSI disks? Maybe in sum situation, with some configuration of iSCSI server, with some specific virt-sparsify options? Shmuel