From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/vagrant/installation%2Findex.html | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 devdocs/vagrant/installation%2Findex.html (limited to 'devdocs/vagrant/installation%2Findex.html') diff --git a/devdocs/vagrant/installation%2Findex.html b/devdocs/vagrant/installation%2Findex.html new file mode 100644 index 00000000..ee69a0d3 --- /dev/null +++ b/devdocs/vagrant/installation%2Findex.html @@ -0,0 +1,26 @@ +

Installing Vagrant

Installing Vagrant is extremely easy. Head over to the Vagrant downloads page and get the appropriate installer or package for your platform. Install the package using standard procedures for your operating system.

The installer will automatically add vagrant to your system path so that it is available in terminals. If it is not found, please try logging out and logging back in to your system (this is particularly necessary sometimes for Windows).

+ +

Running Multiple Hypervisors

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.
+
+Command: ["startvm", <ID of the VM>, "--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
+
+

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.

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
+kvm                   593920  1 kvm_intel
+irqbypass              16384  1 kvm
+
+

The one we're interested in is kvm_intel. You might have another.

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:

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
+
+

You can also disable it by going through the Windows system settings:

You might have to reboot your machine for the changes to take effect. More information about Hyper-V can be read here.

+

+ © 2010–2018 Mitchell Hashimoto
Licensed under the MPL 2.0 License.
+ https://www.vagrantup.com/docs/installation/ +

+
-- cgit v1.2.3