> Looking at the file size isn't helpful. The 23 GB
> are the space that is actually used. You can use 'du -h'
> to confirm this, but I think it gets the number in the exact same way as
> qemu-img.
Are you sure about that? My OS complains that the disk is full. I can't
even start any VM anymore.
We have played a bit around with external snapshots (as suggested by
Eric Blake in post #3), however, it appears that external snapshots are
not fully supported yet. While I can create external snapshots, I'm
unable to revert to them using virt-manager (which we use for managing
our VM farm):
Erro
I don't have many commands handy, as we manage almost everything through
libvirt manager.
3) create a snapshot of the lined clone:
virsh snapshot-create-as --domain --name "test" --halt
4) revert the snapshot every X minutes / hours:
virsh destroy
virsh snapshot-revert --snapshotname test --r
Public bug reported:
I've recently migrated our VM infrastructure (~200 guest on 15 hosts)
from vbox to Qemu (using KVM / libvirt). We have a master image (QEMU
QCow v3) from which we spawn multiple instances (linked clones). All
guests are being revert once per hour for security reasons.
About 2
