Libvirt provider's storage_pool_name option and virsh setup inconsistency

[Johan Mazel]

Hello

I am using libvirt 6.9.0 and Vagrant 2.2.9 on a Debian Testing.

I setup a storage pool named "default " that is visible using "virsh pool-list --all" using the documentation at this URL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/sect-virtualization-storage_pools-creating-local_directories-virsh.

Using the virt-install commands from https://wiki.debian.org/KVM#Creating_a_new_guest, I manually verified that this "default" storage pool is working (ie the VM image is added to my custom directory).

I however have a problem when I set the "storage_pool_name" option to "default" in the libvirt provider part of the VagrantFile.

When I do "vagrant up --provider libvirt, the box and images are created in the default directory (ie /var/lib/libvirt/), not the other "default" storage pool I previously setup.

I also created another storage pool with a name different than "default".

When I set the storage_pool_name option to this other name, I get: "No usable storage pool found! Please check if storage pool is created and available."

My hypothesis is that vagrant is using the libvirtd service to manage boxes and VM images, and that this service is not using the same storage pools as the ones exposed by "virsh pool-list --all".

Does anybody know how to fix this problem?

Thank you for your time.

Best regards,

Johan Mazel