It seems every time I create a VM with virt-install a new storage pools is created.
But I don’t use storage pools at all.
I looked in the virt-install manual but could find a way to prevent this from happening.
Also been looking for any settings in the libvirt/qemu config file to disable storage pools in any way but couldn’t find anything there either.
If I run “virsh pool-capabilities” I do get a XML output with some “supported” attribute which could be interesting to set to ‘no’ but again I cannot find anywhere edit those settings.
KVM stores guest images in storage pools. The default pool is /var/lib/libvirt/images but you can create a storage pool anywhere. As far as I’m aware, if you create a storage volume, you have to place it in a storage pool. I don’t think there is any way around this. I think you can import an existing disk image that is not in a pool, but you cannot create one outside of a pool. In any case, the storage pool is just informing libvirt where your disk images are located.
kvm/qemu/libvirt runs fine without storage pools. I specify the direct filesystem-path to the qcow2 image-files in the VM XML and I always (when I remember) clean up (completely deletes) ALL storage pools, incl. default and those auto-created pools and libvirt work fine.