On Sat, Jan 27, 2018 at 01:04:32PM +0000, OmegaPhil wrote: > Using Virtual Machine Manager 1.4.3 here on Devuan Ascii with libvirt0 > 3.0.0-4+deb9u1. I have a collection of VMs on this machine (so single > host, no migrations, no shared storage etc etc) that are stored in a > storage pool outside of the root volume (since the root volume is mostly > dedicated to the OS) - so not '/var/lib/libvirt/images'. > > The OS volume is running out of space, and I found that snapshots were > being stored separately from the VMs, at '/var/lib/libvirt/qemu/save' - > is there a way for me to configure where snapshots end up, and > preferably in the same storage location as the VMs? > > '/etc/libvirt/storage' seems to only store configuration for the storage > pools that host the VMs. > > Thanks for any help Hi, So you are not probably talking about snapshot but about suspending the guests. Currently virt-manager uses internal snapshots and it works only for qcow2 disk images, the snapshot itself is stored inside that disk image. The path "/var/lib/libvirt/qemu/save" is used for "saving" the virtual machine. This is handled by libvirt, virt-manager only controls libvirt, and unfortunately there is no way how to change the default path. The only suggestion is that you can mount different volume under that path to not use the root one. Pavel
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
