Error creating machine: Error in driver during machine creation: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory #2256
Comments
I believe the error message tells you what's wrong and what to do:
You need to go into your laptop BIOS and enable VT-X/AMD-v. |
Thanks for the response! Actually, I am on vmware and it's one of the VMs, headless. I am not the admin of the machine, but I suppose it is still possible to configure it? |
So, you are inside a VMWare VM and trying to start virtualbox inside it? |
yes, I am on the VM server (not physical) and trying to create docker machine with the virtualbox docker inside that VM. |
I do have VirtualBox inside of VMware Fusion working on a VM on my laptop, you have to toggle a setting in the Preferences menu for the VM to get nested virtualization to work though. |
@GiantEnemyCrab If our VTX check is preventing you from being able to make a VM when you otherwise could (e.g. with older versions of Machine), then we should fix it, but check to make sure creating any VM at all works please. |
Thanks for the feedback so far to both of you. The older versions, I could try 0.4.1 or 0.4.0 and come back here with results. |
I am back here with some results. It looks like the machine itself is created in 0.4.1, I think..... Anyway, I will paste the debug log here. VBox.log file: https://gist.github.com/GiantEnemyCrab/42187e86f4867028dced |
Hi @GiantEnemyCrab, before version 0.5.0, the vm was looping attempting ssh connection because the vm could in fact not be started. With version 0.5.0, the exact error is now displayed. |
ok, I somehow switched the version of virtualbox to 4.3 default, let me try with 5.0.8 again, sorry about this, and will be back with some results. |
To make sure that there's really a problem with the created vm, you can capture its screen with |
Thanks @dgageot, I got the screenshot. And there is a message before the docker whale ascii art saying:
In this case, at least, VM is created using 0.4.1? But weird, the CPU is indeed x86_64.
Hmmmm, how can I move forward? |
Hi @GiantEnemyCrab The thing is you are running VirtualBox inside VMWare VM. So even if the host is a x86-64 with hardware virtualization enabled, there's a good chance that Virtualbox isn't able to use those VT-X instructions. |
Click on VM => "Virtual Machine" menu => Preferences => Processors and Memory => Advanced options => Enable hypervisor applications in this virtual machine |
Thank you so much for the insight! It turns out that since I am already in Ubuntu, I don't really need to do the virtualbox stuff. I can just docker create / docker run by pulling an image, such as postgres and it can run just fine. I was blindly trying to follow instructions specifically for windows / mac, but it does not look like I need the initial docker-machine create default part anyway. Please confirm that, and I think the error message given about VT-X, etc, is appropriate in docker-machine v0.5.0. In that case the ticket can be closed. However, @nathanleclaire 's preference editing is a great reference as well. |
@GiantEnemyCrab Great! Let's close this ticket then. |
Nicely done everyone 👍 |
This solution works for me.(Window 10/8)
|
Have same problem on my Windows 7 Enterprise laptop running a Ubuntu OS VM using Oracle VirtualBox. However, I do see Virtualization enabled on my Windows laptop as well as on Ubuntu VM. The Oracle VirtualBox includes System Acceleration Setting: VT-x/AMD-V, Nested Paging, Hyper-V ParaVirtualization on the Ubuntu VM, I tried the default paravirtualization as well, but of no use. My windows laptop (has its own windows OS - docker issues) is able to start docker containers on created docker-machine on my laptop but not on Ubuntu VM, Everything is messed up if I use docker-machine comands on my Ubuntu VM.
|
VMWare Workstation/Fusion - Ubuntu VM (64bit 16.04) sudo apt-get install virtualbox https://github.com/docker/labs/blob/master/swarm-mode/beginner-tutorial/swarm-node-vbox-setup.sh Worked just fine. |
$ sudo docker-machine create --driver virtualbox manager1 Please note i am using AWS ubuntu 16.04 machine |
I run a command like:
I get
Here is my environment
Would be great if anybody could point me to resolve this.
Here is the --debug output: https://gist.github.com/GiantEnemyCrab/633c6c7e9f8fd929d348
And here is the VBox.log: https://gist.github.com/GiantEnemyCrab/43f3f9990af26deec4c8
The text was updated successfully, but these errors were encountered: