VT-x error not available for Vagrant machine inside Virtualbox

Question

I have a Ubuntu virtual machine that is configured to enable VT-x, 6 processors and 25 GB of RAM.

Inside this virtual machine, I am trying to start a vagrant machine with the following configuration:

master.vm.box = "precise32" master.vm.provider "virtualbox" do |vb| vb.customize ["modifyvm", :id, "--cpuexecutioncap", "80"] vb.memory = 10000 vb.customize ["modifyvm", :id, "--cpus", "2"] vb.customize ["modifyvm", :id, "--ioapic", "on"] end 

When I start a tramp, I get a VT-x error not included.

I tried both the 32-bit and 64-bit versions of Vagrant, but still no luck.

Any idea how I can run a Vagrant machine inside Virtualbox?

Answer 1

UPDATED: As indicated below, you can use the nested VirtualBox + vagrant provided that only 1 virtual processor is assigned to the nested virtual machine, plus the 32-bit OS nested guest guest guest computer.

Answer 2

You can use only one virtual processor without VT-x. Thus, an error message indicating that VT-x is not activated is caused by the following line:

vb.customize ["modifyvm", :id, "--cpus", "2"]

Replacing it with the following works (Vagrant has a shortcut for setting the number of CPUs):

vb.cpus = 1

NOTE. You can only run 32-bit virtual machines inside another virtual machine.

Answer 3

Vagrant in a nested virtual box

First of all, you can run Vagrant specifically inside a nested virtual box.

VT-X Support (associated with VirtualBox)

VirtualBox does not currently support VT-X nesting. A function request is currently expected (see: https://www.virtualbox.org/ticket/4032 ), but at the moment it is not expected in the new version of VirtualBox

Consequences of Missing VT-X in a Nested VirtualBox

There are currently two consequences of nesting without VT-X:

• You cannot use multiple processors, but you can use one virtual processor with vb.cpus = 1
• You cannot start a 64-bit virtual machine inside a nested VirtualBox.

Answer 4

You cannot use the first virtual machine as a virtual box. That's for sure. But what you can do, make the first virtual machine (Ubuntu) based on VMware Player 7, then you can configure Vagrant for this. Tested and verified independently. VMplayer version 7 and Virtual Box version 5.0.20. Thanks to Rudolph's comment on the same page

Answer 5

If you run vagrant + VirtualBox inside a VirtualBox virtual machine and encounter network problems:

Remember to install the correct virtual network adapter

I had to install Adapter Type on Paravirtualized Network (virtio-net)

in Settings → Network → Advanced to make it work

Answer 6

VirtualBox inside VirtualBox is not working. Try VMPlayer and then install VirtualBox and the tramp inside. His work is for me.