storage pool may not exist -- KVM

[busser]

When using KVM, vagrant fails if storage pool does'nt exists, which is the case by default.
storage pool is configured to "hdp-cluster", but there is no checks for existence, nor auto creation script !!

--> Default conf is not working by default !

[Nuttymoon]

Hey there, thanks for trying Jumbo! Indeed, that's something we forgot to automize when open sourcing!
hdp-cluster is not a good name for the storage pool by the way. We will add this to the TODO list.
What has to be done is write a python script that creates a pool named jumbo-clusters if it doesn't exist by leveraging virsh and put it in the script section of the setup.py.

[Pierrotws]

With jumbo-clusters default location on ~/.jumbo/storage for example ?

[Nuttymoon]

Solved in v0.4.4 (commit: 05765c0).
At installation, a storage pool jumbo-storage is created in /var/lib/libvirt/images/jumbo-storage.