On Mon, Sep 17, 2018 at 03:16:05PM +0200, Lucas Nussbaum wrote: > On 15/09/18 at 09:46 -0300, Antonio Terceiro wrote: > > On Fri, Sep 14, 2018 at 05:10:48PM +0200, Lucas Nussbaum wrote: > > > Package: vagrant > > > Version: 1.9.1+dfsg-1+deb9u1 > > > Severity: normal > > > > > > Hi, > > > > > > vagrant 1.9.1+dfsg-1+deb9u1 is now incompatible with virtualbox from > > > stretch-backports (version 5.2.18-dfsg-1~bpo9+1). It worked fine with > > > virtualbox 5.1.30-dfsg-1~bpo9+1. > > > > > > vagrant from stretch-backports works fine with virtualbox from > > > stretch-backports. > > > > > > When starting vagrant, I get: > > > $ vagrant up > > > No usable default provider could be found for your system. > > > > > > Vagrant relies on interactions with 3rd party systems, known as > > > "providers", to provide Vagrant with resources to run development > > > environments. Examples are VirtualBox, VMware, Hyper-V. > > > > > > The easiest solution to this message is to install VirtualBox, which > > > is available for free on all major platforms. > > > > > > If you believe you already have a provider available, make sure it > > > is properly installed and configured. You can see more details about > > > why a particular provider isn't working by forcing usage with > > > `vagrant up --provider=PROVIDER`, which should give you a more specific > > > error message for that particular provider. > > > > > > (while of course virtualbox is available, and works fine outside of > > > Vagrant) > > > > Can you please test the .deb from > > https://people.debian.org/~terceiro/tmp/vagrant-stretch/ > > ? > > Sorry for the delay. > > It doesn't work. It doesn't find the virtualbox provider (it uses > libvirt), and when forced, it says that it doesn't support 5.2.
Right - I noticed there was one missing bit. Can you grab the .deb from the above URL and try again? sorry for making you test it for me, but I don't have an easy way to get a VirtualBox-capable system running stretch
signature.asc
Description: PGP signature
