From 80d77e934ffc10413f1b100a461e6ddfd23fc384 Mon Sep 17 00:00:00 2001 From: "Richard W.M. Jones" Date: Wed, 12 Mar 2014 21:39:18 +0000 Subject: [PATCH] FAQ: Document virt-sparsify >= 1.26 can do in-place sparsification. --- examples/guestfs-faq.pod | 20 +++++--------------- 1 file changed, 5 insertions(+), 15 deletions(-) diff --git a/examples/guestfs-faq.pod b/examples/guestfs-faq.pod index 85564a1ab..923c9b3f7 100644 --- a/examples/guestfs-faq.pod +++ b/examples/guestfs-faq.pod @@ -692,22 +692,12 @@ so we are reluctant to change it. =head2 Why doesn't virt-sparsify work on the disk image in-place? -Eventually we plan to make virt-sparsify work on disk images in-place, -instead of copying the disk image. However it requires several -changes to both the Linux kernel and qemu which are slowly making -their way upstream (thanks to the tireless efforts of Paolo Bonzini). -Then we will have to modify virt-sparsify to support this. Finally -there will be some integration work required to make sure all the -pieces work together. +In libguestfs E 1.26, virt-sparsify can now work on disk images in +place. Use: -Even with this implemented there may be some limitations: For example, -it requires completely different steps (and is probably harder) to -sparsify a disk image that is stored on a SAN LUN, compared to one -which is stored in a local raw image file, so you can expect that -different storage and backing formats will become supported at -different times. Some backing filesystems / formats may never support -sparsification (eg. disk images stored on VFAT, old-style non-thin -LVs). + virt-sparsify --in-place disk.img + +But first you should read L. =head1 PROBLEMS OPENING DISK IMAGES