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 ?

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.

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

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

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

ok so I was having the same issue with windows, vagrant and virtualbox and did this.

1. click on "This PC" / "My Computer" on windows desktop
2. Select "Properties"
3. Go to "Advanced" tab
4. Click "Environment Variables..." at the bottom
5. Under System Variables click "New..."
6. Set "Variable name" to "VBOX_INSTALL_PATH"
7. Set "Variable value" to "C:\Program Files\Oracle\VirtualBox"
8. Select "OK" and close all the other settings windows

credit goes to here: https://github.com/mitchellh/vagrant/issues/3852

I am assuming that there is a Environment Variable ( or PATH for linux users I think :P) that needs the "path" to the virtualbox executable.

I'm running macOS 10.12 and installed 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).

N.B. This version is labeled amd64 on the download page, this is just the name of the 64 bit standard and will install fine on Intel macs.

I had installed Virtualbox 6.1 and Vagrant 2.2.6 and got this error on a Mac. I had to revert Virtualbox to 6.0 and then vagrant up worked with ubuntu/trusty64. See @Serge Voloshenko's answer above for how to discover if it's a compatibility issue.

It is just the Version problems either it can be problem from vagrant or from Virtual box to connect

Try this : vagrant up --provider VirtualBox

Above command will help if the version of virtual box is compatible or not and it will also suggest which are the current linkable versions of Virtual box

Currently : 4.0,4.1,4.2,4.3,5.0,5.1,5.2 are the versions of virtual box that are working

By the way, If you are worrying about version of Vagrant, I have tried current version : 2.0.3