$ /usr/bin/vagrant version
Installed Version: 2.0.0
Latest Version: 2.0.0
Ubuntu 16.04.3 LTS
Any, doesn't matter.
Doesn't matter, failed with Windows Guest VM or Linux Guest VM.
It should find a VirtualBox-5.2 Provider.
$ /usr/bin/vagrant status
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.
Should be fixed here https://github.com/hashicorp/vagrant/pull/8955 ?
same here! Seems like it was merged after the 2.0.0 release:
Merge Commit on 3. Okt and Release commit on 7. Sep
i've reinstalled the old virtualbox version via brew
brew uninstall virtualbox
brew cask install https://raw.githubusercontent.com/caskroom/homebrew-cask/e8816187ae43f52b598f15f45b3453e22727ac99/Casks/virtualbox.rb
For those, who need also the extension pack, here is a brew install command (for version 5.1.30)
brew cask install https://raw.githubusercontent.com/caskroom/homebrew-cask/f738828d2e69bb5f906929b9e54e66655f39bd48/Casks/virtualbox-extension-pack.rb
I've installed vagrant from the git repository (f99c5d481) using the PKGBUILD vagrant-git.
I confirm it works with Virtual Box 5.2 under Arch Linux.
I just copied the updates from 7d73af5637de41f1e53b8f1ef2ea9baf76842dfb and it worked.
Hey all! Yes....VirtualBox 5.2 support has already been merged into master. However that code has not been put in a release yet. It should go out in the next release of Vagrant. For now, please use the latest VirtualBox 5.1.x! Thanks.
I'm going to lock this issue because it has been closed for _30 days_ โณ. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Most helpful comment
Hey all! Yes....VirtualBox 5.2 support has already been merged into master. However that code has not been put in a release yet. It should go out in the next release of Vagrant. For now, please use the latest VirtualBox 5.1.x! Thanks.