similar to: snapshots and qcow2

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

Hi There, I''ve been trying to get this to work for the last couple of days, but found no information on the internet that would help. Essentially, a tap-ctl opencommand with a qcow2 image does not work (error code 2) and produces the following line in syslog: tap-ctl: tap-err:tap_ctl_open: open failed, err -2 I have attached a shell script that reproduces the problem on my machine. The

Hi guys, I had to move to the new laptop week ago and I screw migration of my virtual machines. I recovered my virtual machines on the new laptop (virsh define) using the backed up xml files, but I am missing any file with metadata about snapshots. The original storage is cleaned so I cannot take these files anymore. Using qemu-info I can see my snapshots inside the qcow images, but libvirt

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

----- Original Message ----- From: "Eric Blake" <eblake@redhat.com> To: "Adam King" <kinga@sghs.org.uk>, libvirt-users@redhat.com Sent: Thursday, August 21, 2014 3:17:09 AM Subject: Re: [libvirt-users] virsh snapshot On 08/20/2014 06:34 PM, Adam King wrote: > Hi, > [Can you convince your mailer to wrap long lines?] > > I had a 'domain' called

hi Martin, thanks again for the feedback. maybe you have noted that I am not yet all too familiar with those tools. this is now sort of working for me. But I sense that you seem this method to be less then ideal. Reading through the virsh manual it looks like ... $ virsh snapshot-create [domain] --disk-only --live ... might be doing a similar thing. Maybe more elegant (pure virsh) and on a

> Your quoting is horrible. You used the same prefix for your original > content as for my reply (">> >" in both cases). I'm not sure what > mailer you are using, but it is making conversation difficult. OK, let's see if this is better. Turned out my email app wasn't doing text wrap and quoting prefix default was bizarre....my apologies. > > >

Hey When I want to take a snapshot for a Domain by using virDomainSnapshotCreateXML. The Error as below happen: libvir: QEMU error : Requested operation is not valid: Disk '/var/lib/libvirt/images/fedora-qcow.qcow2' does not support snapshotting The snapshot Configuration is : <domainsnapshot> <description>Snapshot of OS install and updates</description>

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?

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

I have numerous qcow2 images which need to be reduced in size and have their maximum size (virtual size) reduced. Physical disk space became so low that VMs "auto-paused" themselves, I moved enough images to solve the immediate problem but need to rectify the underlying issue. It seems that qcow[2] files are grown in size such that the data inside of them takes about 50-60% of the

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

I take an internal snapshot (VM is 'shutdown' when taking it) of a qcow2 image like this: $ qemu-img snapshot -c sn1 [my_image].qcow2 I see that snapshot when asking for: $ qemu-img info [my_image].qcow but do NOT see it with: $ virsh domblklist [my_domain] is that how it is meant to be?

Hi, List, I''m trying xl create a pv guest with qcow/qcow2 image, it always fails at libxl_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 disk configuration is: disk=[

If you are using XFS - there is mount option "discard|nodiscard" From XFS man page: discard|nodiscard Enable/disable the issuing of commands to let the block device reclaim space freed by the filesystem. This is useful for SSD devices, thinly provisioned LUNs and virtual machine images, but may have a performance impact. Note: It is currently

I have used virsh snapshot-create-as <VM name> <snapshot name> "<snapshot description>" --diskspec "vda,snapshot=external,file=/path/to/external-snapshot" --disk-only --atomic to create an external snapshot of a running VM. I followed it with virsh blockpull <VM name> --path /path/to/external-snapshot and monitored it until done.

I''ve been using lvm under centos to create the backing store for domUs and although the performance seems acceptable it has some shortcomings. The biggest of which is the LVM bug which prevents me from removing an lv (it says it is still mounted and it definitely isnt). I thought this was just a centos bug but it appears to be evident in debian and ubuntu too and I really can''t

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

Hi all, I'm using ZFS on Linux block volumes as my VM storage and want to do live migrations between hypervisors. If I create ZFS snapshot of used volume on source host, send it do destination host (zfs send/recv) and then run live migration with VIR_MIGRATE_NON_SHARED_DISK flag, the migration works OK. But this procedure copies the whole disk twice which is a huge downside. The best

On Mon, Jul 31, 2017 at 08:28:49AM -0500, Leroy Tennison wrote: > I realize this is wandering off-topic but, if you have found Debian commands, you're doing better than me. What are they? Also, are you allowing dd to totally fill the partition (what I have found on the web as a recommendation)? If so, is the OS surviving acceptably? > > ----- Original Message ----- > From: