Vagrant-libvirt: ERROR: Call to virStoragePoolDefineXML failed: operation failed: pool 'default' already exists

Created on 6 Jan 2016 · 7Comments · Source: vagrant-libvirt/vagrant-libvirt

# vagrant up
Vagrant.require_plugin is deprecated and has no effect any longer.
Use `vagrant plugin` commands to manage plugins. This warning will
be removed in the next version of Vagrant.
Bringing machine 'test_vm' up with 'libvirt' provider...
There was error while creating libvirt storage pool: Call to virStoragePoolDefineXML failed: operation failed: pool 'default' already exists with uuid 69266e1a-18f9-4e1f-98ed-d105ad8ba0d5
# vagrant --version
Vagrant 1.7.4
# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu 15.10"

Source

d33tah

Most helpful comment

I ran into this issue earlier this morning, it was caused by the default pool being defined but not active:

virsh # pool-list --all

Name State Autostart

default inactive no
Downloads active yes
...

Activating the default pool resolved the issue:
virsh # pool-start default

jcsmith on 27 Jan 2016

👍6

All 7 comments

@pradels: Ping. Any chance this could be resolved?

d33tah on 9 Jan 2016

no chance if you will not sent pull request.

pronix on 9 Jan 2016

@pronix: hmm... I don't know libvirt enough to fix that. Is there any way you could help me debug that?

d33tah on 9 Jan 2016

you can just rename default pool - it will created, or you should remove existed.

pronix on 9 Jan 2016

That's interesting! virsh says that the pool isn't there and when I used --provider libvirt instead of exporting that, I got the machine up. Thanks @pronix!

d33tah on 9 Jan 2016

I ran into this issue earlier this morning, it was caused by the default pool being defined but not active:

virsh # pool-list --all