haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add message about hyper-v and virtualbox

This commit is contained in:
Brian Cain 2018-07-27 16:18:42 -07:00
parent 6b022bcbfb
commit f7b0fbeb88
No known key found for this signature in database
GPG Key ID: 43D51080D357A001
1 changed files with 33 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
website/source/docs/installation/index.html.md
View File

@ -37,10 +37,12 @@ necessary sometimes for Windows).
experience issues. Please use the official installers on the downloads page. experience issues. Please use the official installers on the downloads page.
</div> </div>
## If You're Running Other Virtualizers on Linux ## Running Multiple Hypervisors
On some systems you may get the following error when running Vagrant Sometimes, certain hypervisors do not allow you to bring up virtual machines
commands: if more than one hypervisor is in use. If you are lucky, you might see the following
error message come up when trying to bring up a virtual machine with Vagrant and
VirtualBox:
There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below. There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.
@ -51,10 +53,16 @@ commands:
(VERR_VMX_IN_VMX_ROOT_MODE) (VERR_VMX_IN_VMX_ROOT_MODE)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
This is because another virtualizer (like KVM) are in use. We must blacklist Other operating systems like Windows will blue screen if you attempt to bring up
these in order for VirtualBox to run correctly. a VirtualBox VM with Hyper-V enabled. Below are a couple of ways to ensure you
can use Vagrant and VirtualBox if another hypervisor is present.
First find out the name of the virtualizer: ### Linux, VirtualBox, and KVM
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:
$ lsmod | grep kvm $ lsmod | grep kvm
kvm_intel 204800 6 kvm_intel 204800 6
@ -63,8 +71,26 @@ First find out the name of the virtualizer:
The one we're interested in is `kvm_intel`. You might have another. The one we're interested in is `kvm_intel`. You might have another.
Blacklist the virtualizer (run the following as root): Blacklist the hypervisor (run the following as root):
# echo 'blacklist kvm-intel' >> /etc/modprobe.d/blacklist.conf # echo 'blacklist kvm-intel' >> /etc/modprobe.d/blacklist.conf
Restart your machine and try running vagrant again. 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 enabled
on Windows. You can turn off the feature by running this Powershell command:
```powershell
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
```
You can also disable it by going through the Windows system settings:
- Right click on the Windows button and select ‘Apps and Features’.
- Select Turn Windows Features on or off.
- Unselect Hyper-V and click OK.
You might have to reboot your machine for the changes to take effect. More information
about Hyper-V can be read [here](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v).