» Installing Vagrant

The installer will automatically add to your system pathso that it is available in terminals. If it is not found, please trylogging out and logging back in to your system (this is particularlynecessary sometimes for Windows).

Looking for the gem install? Vagrant 1.0.x had the option tobe installed as a .This installation method is no longer supported. If you have an old versionof Vagrant installed via Rubygems, please remove it prior to installing newerversions of Vagrant.

Beware of system package managers! Some operating systemdistributions include a vagrant package in their upstream package repos.Please do not install Vagrant in this manner. Typically these packages aremissing dependencies or include very outdated versions of Vagrant. If youinstall via your system's package manager, it is very likely that you willexperience issues. Please use the official installers on the downloads page.

Other operating systems like Windows will blue screen if you attempt to bring upa VirtualBox VM with Hyper-V enabled. Below are a couple of ways to ensure youcan use Vagrant and VirtualBox if another hypervisor is present.

The above error message is because another hypervisor (like KVM) is in use.We must blacklist these in order for VirtualBox to run correctly.

First find out the name of the hypervisor:

Blacklist the hypervisor (run the following as root):

Restart your machine and try running vagrant again.

» Windows, VirtualBox, and Hyper-V

If you wish to use VirtualBox on Windows, you must ensure that Hyper-V is not enabledon Windows. You can turn off the feature by running this Powershell command:

• Select Turn Windows Features on or off.