From 6b022bcbfb52ddb6a24a3d2eb5b3631afa394e92 Mon Sep 17 00:00:00 2001 From: Jordan Hewitt <1633901+src-r-r@users.noreply.github.com> Date: Tue, 12 Jun 2018 08:44:41 -0700 Subject: [PATCH 1/2] Added note on other virtualizers before pre-install. --- .../source/docs/installation/index.html.md | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/website/source/docs/installation/index.html.md b/website/source/docs/installation/index.html.md index 196a98dee..2ea4cf864 100644 --- a/website/source/docs/installation/index.html.md +++ b/website/source/docs/installation/index.html.md @@ -36,3 +36,35 @@ necessary sometimes for Windows). install via your system's package manager, it is very likely that you will experience issues. Please use the official installers on the downloads page. + +## If You're Running Other Virtualizers on Linux + +On some systems you may get the following error when running Vagrant +commands: + + There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below. + + Command: ["startvm", , "--type", "headless"] + + Stderr: VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE). + VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot + (VERR_VMX_IN_VMX_ROOT_MODE) + 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 +these in order for VirtualBox to run correctly. + +First find out the name of the virtualizer: + + $ lsmod | grep kvm + kvm_intel 204800 6 + kvm 593920 1 kvm_intel + irqbypass 16384 1 kvm + +The one we're interested in is `kvm_intel`. You might have another. + +Blacklist the virtualizer (run the following as root): + + # echo 'blacklist kvm-intel' >> /etc/modprobe.d/blacklist.conf + +Restart your machine and try running vagrant again. From f7b0fbeb88c088b54bd0e3d49e4d1e14aabda80a Mon Sep 17 00:00:00 2001 From: Brian Cain Date: Fri, 27 Jul 2018 16:18:42 -0700 Subject: [PATCH 2/2] Add message about hyper-v and virtualbox --- .../source/docs/installation/index.html.md | 40 +++++++++++++++---- 1 file changed, 33 insertions(+), 7 deletions(-) diff --git a/website/source/docs/installation/index.html.md b/website/source/docs/installation/index.html.md index 2ea4cf864..14df7a1cc 100644 --- a/website/source/docs/installation/index.html.md +++ b/website/source/docs/installation/index.html.md @@ -37,10 +37,12 @@ necessary sometimes for Windows). experience issues. Please use the official installers on the downloads page. -## If You're Running Other Virtualizers on Linux +## Running Multiple Hypervisors -On some systems you may get the following error when running Vagrant -commands: +Sometimes, certain hypervisors do not allow you to bring up virtual machines +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. @@ -51,10 +53,16 @@ commands: (VERR_VMX_IN_VMX_ROOT_MODE) 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 -these in order for VirtualBox to run correctly. +Other operating systems like Windows will blue screen if you attempt to bring up +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 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. -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 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).