Failed to roam - how to establish "suppliers",

Question

I try to start a tramp, but after a vagrant up error 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. 

I installed before VirtualBox version 4.3.26 r989888 and Linux Ubuntu (64 bit)

After: vagrant box add precise32 http://files.vagrantup.com/precise32.box

==> box: Adding box 'precise32' (v0) for provider: box: Downloading: http://files.vagrantup.com/precise32.box box: Progress: 100% (Rate: 1425k/s, Estimated time remaining: --:--:--) ==> box: Successfully added box 'precise32' (v0) for 'virtualbox'!

when i list vagrant box list

 lucid32 (virtualbox, 0) precise32 (virtualbox, 0) 

What happened to the "provider"

vagrant package --base vagrant-ubuntu64

 Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires this to be available on the PATH. If VirtualBox is installed, please find the `VBoxManage` binary and add it to the PATH environmental variable. 

How to help him discover VirtualBox?

Answer 1

Quick Note - Vagrant 1.8.4 and Virtualbox 5.1.X are not compatible with MacOS 10.11 (vendor cannot be installed).

Virtualbox 5.0.10 works great.

Answer 2

I was able to fix this simply by installing the latest version of Vagrant (starting with this post 1.7.4).

Answer 3

ok, so I ran into the same issue with windows, stroller and virtual boxing and did it.

• Click "This Computer" / "My Computer" on the Windows desktop
• Select "Properties"
• Go to the Advanced tab
• Click "Environment Variables ..." at the bottom
• In the System Variables section, click Create ...
• Set "Variable Name" to "VBOX_INSTALL_PATH"
• Set "Variable Value" to "C: \ Program Files \ Oracle \ VirtualBox \"
• Select "OK" and close all other settings windows.

the loan goes here: https://github.com/mitchellh/vagrant/issues/3852

I assume that there is an environment variable (or PATH for Linux users who, it seems to me, P) that needs a "path" to the virtual block executable.

Answer 4

It seems like using VirtualBox 4.3.12 issue :

VirtualBox automatically creates the following environment variable VBOX_MSI_INSTALL_PATH

However, a tramp (if you are looking for the base.rb file), the variable VBOX_INSTALL_PATH

So you can - update the variable name VBOX_MSI_INSTALL_PATH and change it to VBOX_INSTALL_PATH - create a new variable name VBOX_INSTALL_PATH with the same value as VBOX_MSI_INSTALL_PATH

Reminder in windows goes to My Computer (right click) --> Properties --> Advanced System Settings --> Environment Variables and looks for the variable you need to manage

Answer 5

just try bringing the stroller up and indicating the provider you want to use:

 vagrant up --provider virtualbox 

As shown in the screenshot below, it will tell you the reason why the specified provider is not working. In my case, it was an unsupported version of VirtualBox 5.2. I had to downgrade it to version 5.1

Answer 6

I am running macOS 10.12 and installing vagrant 5.1 using homebrew.

I got the same error as the OP and fixed it by downloading the latest version of VirtualBox (v5.1.6).

NB This version is marked as amd64 on the download page, it is just the name of the 64-bit standard and will be perfectly installed on Mac Mac.