similar to: IRC question: virt-builder & size of qcow2 output files

After snapshot-delete, the qcow2 image file size doesn't decrease, isn't that a waste of disk space? Would someone please tell me how to decrease the file size when snapshot-delete, if that's possible? The image file name of my virtual machine is d0.qcow As follows: [root at test1 ]# virsh list Id Name State

On Tue, May 17, 2016 at 6:01 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, May 17, 2016 at 05:53:31PM +0300, Yaniv Kaul wrote: > > On Tue, May 17, 2016 at 5:48 PM, Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > > > > On Tue, May 17, 2016 at

On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > When creating qcow2 images using virt-builder, is there a way to specify > the qcow2 preallocation, as possible with qemu-img create -o > preallocation=metada , for example? No .. but .. it does default to preallocation=metadata provided that the output format is qcow2:

On Tue, May 17, 2016 at 5:48 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > > When creating qcow2 images using virt-builder, is there a way to > specify > > > the qcow2 preallocation, as possible with qemu-img create -o

On Tue, May 17, 2016 at 05:53:31PM +0300, Yaniv Kaul wrote: > On Tue, May 17, 2016 at 5:48 PM, Richard W.M. Jones <rjones@redhat.com> > wrote: > > > On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > > > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > > > When creating qcow2 images using virt-builder, is there a way to

When creating qcow2 images using virt-builder, is there a way to specify the qcow2 preallocation, as possible with qemu-img create -o preallocation=metada , for example? TIA, Y.

On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > When creating qcow2 images using virt-builder, is there a way to specify > > the qcow2 preallocation, as possible with qemu-img create -o > > preallocation=metada , for example? > > No .. but .. it does default to preallocation=metadata

On Tue, Jun 02, 2015 at 09:14:03AM +0530, Jatin Davey wrote: > Hi All > > I was reading through this: > > http://kashyapc.com/2011/12/02/little-more-disk-io-perf-improvement-with-fallocateing-a-qcow2-disk/ In my testing, the above method gives near-raw performance as it preallocated all the space ahead of time. The above test can now be done in a single command -- see option (3)

Il 30-01-2018 13:17 Gionatan Danti ha scritto: > Hi all, > on a fully patched CentOS 7.4 x86-64, I see the following behavior: > > - when creating a new volumes using vol-create-as, the resulting file > is a qcow2 version 2 (compat=0.10) file. Example: > > [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 > 8589934592 --format=qcow2 --backing-vol

I found guestfs_compress_out do the compression to gzip, bzip2, compress...etc. I want to compress qcow2, and I found details about qcow2 compression in https://people.gnome.org/~markmc/qcow-image-format.html The QCOW format supports compression by allowing each cluster to be > independently compressed with zlib. Can I do that with guestfs_compress_out?

On 12/08/2014 03:03 PM, Laszlo Hornyak wrote: > Hi, > > I ran into a strange behavior with libvirt snapshots. I have some vms > running with thin-provisioned qcow2 disk images (libvirt 1.1.3 with fedora > 20). > * When I create a snapshot on the VM, the qcow file suddenly grows big, > somewhat bigger than the maximum size of the disk. The maximum (guest) size of a disk is

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 those to be the same, just figured I would show them both for

Hi all, on a fully patched CentOS 7.4 x86-64, I see the following behavior: - when creating a new volumes using vol-create-as, the resulting file is a qcow2 version 2 (compat=0.10) file. Example: [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img Vol zzz.qcow2 created [root@gdanti-lenovo vmimages]# file

I''m trying to create a pv guest with qcow/qcow2 disk image by xl, it always fails atlibxl_device_disk_local_attach. #xl create pv_config_file libxl: error: libxl.c:1119:libxl_device_disk_local_attach: cannot locally attach a qdisk image if the format is not raw libxl: error: libxl_create.c:467:do_domain_create: failed to run bootloader: -3 Does that mean we cannot create such a pv guest

On Wed, Nov 21, 2018 at 11:33:33AM +0800, Han Han wrote: > Hello, I face a problem on the nbdkit server: > > Version-Release number of selected component (if applicable): > nbdkit-v1.9.1 > qemu-utils-2.12+dfsg-3+b1 > > How reproducible: > 100% > > Steps: > 1. Create a qcow2 file > # qemu-img create disk 1G -f qcow2 This creates a 1GB virtual size qcow2 (real

Hi, I ran into a strange behavior with libvirt snapshots. I have some vms running with thin-provisioned qcow2 disk images (libvirt 1.1.3 with fedora 20). * When I create a snapshot on the VM, the qcow file suddenly grows big, somewhat bigger than the maximum size of the disk. * When I delete the snapshot, the allocated disk space is not freed up, the qcow image remains the same size. However, if

Hello, I''m having some problems with hvm images and qcow2 under xen 3.4. The virtual machine won''t boot, and I ignore why. This is the template I''m using: ******** kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' name = "CentosMinimalkvm" memory = 1024 vcpus = 1 boot="c" on_poweroff = "destroy" on_reboot =

Thanks for letting me know I'm not making myself clear, let me try again with a few more specifics, These are Windows VMs with three disk images for C:, D: and L:. To simplify I'll focus on the image for C: which had grown to 77G physical size on the hypervisor's ssd (I just double-checked that with 'ls -al' because qemu-img below says 70G, this image had two snapshots at one

All, is it possible to create a new KVM machine from an existing qcow (v3) image with snapshots? snapshot-list doesn't show them, when using virt-manager 1:1.5.1-0ubuntu1.1 to create the machine. * t-ad5.img: QEMU QCOW Image (v3), 42949672960 bytes chris@cd:/data/md0$ qemu-img snapshot -l t-ad5.img Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1

On Mon, Dec 28, 2015 at 03:36:53PM -0800, Ryan Sawhill Aroha wrote: > Hi there > > The repo definition at http://libguestfsorg/download/builder/index > contains `format=raw` data for each template, eg: > > ``` > [centos-6] > name=CentOS 66 > osinfo=centos66 > arch=x86_64 > file=centos-6.xz > revision=6 >