On 02/05/17 13:13, Pavel Valena wrote: >> On 25/04/17 13:38, Laurentiu Pancescu wrote: >> I changed the test to use the upstream versions of Vagrant and >> vagrant-libvirt (we already used the VirtualBox packages from Oracle). >> Vagrant 1.9.4, the newest release, doesn't recognize vagrant-libvirt, so >> the test fails - I'm using Vagrant 1.9.3 for the time being, that >> version works. > > I am working on the sclo-vagrant1 SCL update. Thanks for the heads-up regarding the vagrant version usability. I will push to testing the new SCL builds ASAP(ETA < 1 month) It seems a bit more nuanced than I thought: upstream vagrant-libvirt only supports Vagrant 1.5 to 1.8. [1] There's also a table with build failures on Vagrant 1.9.1 if you scroll up. For some reason, 1.9.3 worked on CentOS Linux 7 with vagrant-libvirt and 1.9.4 didn't, but 1.9.x is clearly not a supported configuration - not yet. With KVM as the default virtualization on CentOS, fully supported, and VirtualBox not even packaged in our repos (not to mention kernel tainting), wouldn't it be better to upgrade the SCL version to another 1.8.x version instead of the current 1.9 series? Perhaps 1.8.6, it worked reliably for me for a long time and it would support both KVM and VirtualBox 5.1. Thanks, Laurențiu [1] https://github.com/vagrant-libvirt/vagrant-libvirt#installation