Unable to vagrant up - how to set "providers"

I am trying run vagrant but after vagrant up error appears:

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 is wrong with "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 detect VirtualBox ?

Solution 1:

Quick note - Vagrant 1.8.4 and Virtualbox 5.1.X aren't compatible on MacOS 10.11 (can't set a provider).

Virtualbox 5.0.10 works just fine.

Solution 2:

I was able to fix this simply by installing the latest version of Vagrant (as of this writing 1.7.4).

Solution 3:

simply try to bring vagrant up and specify provider you want to use:

vagrant up --provider virtualbox

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

Solution 4:

There seems to have been an issue reported since VirtualBox 4.3.12:

VirtualBox automatically create the following environment variable VBOX_MSI_INSTALL_PATH

However, vagrant (if you look for the base.rb file) uses 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 on windows go to My Computer (right click) --> Properties --> Advanced System Settings --> Environment Variables and look for the variable you need to manage