Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory #4271

Closed
dagonpal opened this issue Oct 6, 2017 · 23 comments

Comments

@dagonpal
Copy link

@dagonpal dagonpal commented Oct 6, 2017

Helo;

I ´m starting with Docker, and I´m following this explample (previously I did the parts 1,2 and 3 without problem):

When I run:

docker-machine create --driver virtualbox myvm1

I recive:

[root@localhost tmp]# docker-machine create --driver virtualbox myvm10
Running pre-create checks...
Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"

This is my environment:

[root@localhost tmp]# docker --version
Docker version 17.10.0-ce-rc1, build d866876

[root@localhost tmp]# docker-machine --version
docker-machine version 0.12.2, build 9371605
[root@localhost tmp]# vboxmanage --version
5.1.28r117968

[root@localhost tmp]# cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core)

This server is running on host with windows 2012 and Hyper-v

Windows Server 2012-R2 (Microsoft Windows [Version 6.3.9600])
Hyper-v Product version: 6.3.6900.18623

@dagonpal

This comment has been minimized.

Copy link
Author

@dagonpal dagonpal commented Oct 9, 2017

Can someone help me?

@matt9ucci

This comment has been minimized.

Copy link

@matt9ucci matt9ucci commented Oct 9, 2017

See this blog post: "Nested Virtualization"

Hyper-V relies on hardware virtualization support (e.g. Intel VT-x and AMD-V) to run virtual machines. Typically, once Hyper-V is installed, the hypervisor hides this capability from guest virtual machines, preventing guests virtual machines from installing Hyper-V (and many other hypervisors, for that matter).

Both hypervisors need to be the latest versions of Hyper-V. Other hypervisors will not work. Windows Server 2012R2, or even builds prior to 10565 will not work.

@dagonpal

This comment has been minimized.

Copy link
Author

@dagonpal dagonpal commented Oct 10, 2017

Thank you very much @matt9ucci, in this case I think that my only option is install docker on a physical server over Linux.
Best regards.

@thaJeztah

This comment has been minimized.

Copy link
Member

@thaJeztah thaJeztah commented Oct 10, 2017

Looks like the question is answered

@thaJeztah thaJeztah closed this Oct 10, 2017
@gmallir

This comment has been minimized.

Copy link

@gmallir gmallir commented Feb 16, 2018

I was facing this error, I have VM ware workstation installed and a CENTOS running on it, when i try to create virtualbox setup as part of using docker-machine, i get error

Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"

FIX: VM-->Settings--->Processor-->Enable "Virtualize Intel VT-x/EPT "...

This has fixed the issue

@AnirudhMohanKumar

This comment has been minimized.

Copy link

@AnirudhMohanKumar AnirudhMohanKumar commented Feb 20, 2018

my fix...
6116 hvw8a

hope this helps!

@cg1990

This comment has been minimized.

Copy link

@cg1990 cg1990 commented Mar 29, 2018

Thank you very much @AnirudhMohanKumar! This works fine. Perfect

@nirvikk

This comment has been minimized.

Copy link

@nirvikk nirvikk commented Apr 30, 2018

docker-machine create default --virtualbox-no-vtx-check this might help

@tigerneil

This comment has been minimized.

Copy link

@tigerneil tigerneil commented May 4, 2018

thanks. it worked for me. @nirvikk

@Izalan

This comment has been minimized.

Copy link

@Izalan Izalan commented May 25, 2018

I have virtualization enabled but still get that error trying to create docker
Tried docker-machine create default --virtualbox-no-vtx-check - it created a machine but failed to start with " Raw-mode is unavailable courtesy of Hyper-V" error. Any ideas how to move forward?
I am on Win 10 if that matters

@xhchrn

This comment has been minimized.

Copy link

@xhchrn xhchrn commented Jun 4, 2018

@opportus

This comment has been minimized.

Copy link

@opportus opportus commented Oct 3, 2018

On Windows 10 Home, I also had virtualization enabled and still got the error.

@Izalan's linked solution fixes the issue in my case. I resume it here:

  1. PS > bcdedit /set hypervisorlaunchtype off
  2. Make sure Core Isolation is turned off (Windows Defender Security Center> Device Security> Core Quarantine)

@thaJeztah, shouldn't that issue be considered a bug (or a signal that the official doc and/or error message need improvement) and so be re-opened?

@jefflancaster

This comment has been minimized.

Copy link

@jefflancaster jefflancaster commented Jan 5, 2019

Thanks @nirvikk !

@zestllankesh

This comment has been minimized.

Copy link

@zestllankesh zestllankesh commented Apr 16, 2019

What about the aws Windows machine?

I am facing this issue on aws Windows ec2 2012 R2.

I installed Docker Toolbox for Windows on aws ec2 Windows 2012 R2 instance (Instance type is t2.medium)

But I am not able to start any docker machines

@matt9ucci

This comment has been minimized.

Copy link

@matt9ucci matt9ucci commented Apr 16, 2019

@zestllankesh The original question of this issue is about Windows Server 2012-R2 environment. That should be the same situation as yours. Please see my answer.

@zestllankesh

This comment has been minimized.

Copy link

@zestllankesh zestllankesh commented Apr 17, 2019

@zestllankesh The original question of this issue is about Windows Server 2012-R2 environment. That should be the same situation as yours. Please see my answer.

Understood. But my problem is not same as mentioned here.

I have Windows 2012 R2 ec2 running in AWS enviroment. I have no control over hardware.
But I want to run docker on top of the Windows 2012 R2 ec2 instance.

@matt9ucci

This comment has been minimized.

Copy link

@matt9ucci matt9ucci commented Apr 17, 2019

@zestllankesh Currently, nested virturalization is available only in bare metal instances. Please be careful they are much more expensive than t2.medium 😅
https://www.reddit.com/r/aws/comments/993zbz/nested_virtualization_within_ec2_need_advice/

@zestllankesh

This comment has been minimized.

Copy link

@zestllankesh zestllankesh commented Apr 19, 2019

@zestllankesh Currently, nested virturalization is available only in bare metal instances. Please be careful they are much more expensive than t2.medium 😅
https://www.reddit.com/r/aws/comments/993zbz/nested_virtualization_within_ec2_need_advice/

Hehe. Guess I'm screwed then 😜
Thank You for taking time for replying

Cheers ✌️

@payam1985

This comment has been minimized.

Copy link

@payam1985 payam1985 commented Aug 12, 2019

docker-machine create default --virtualbox-no-vtx-check this might help

tanks so much, i have same issue so with this line resolved

@RajatKD

This comment has been minimized.

Copy link

@RajatKD RajatKD commented Aug 13, 2019

@nirvikk thanks, your solution worked for me in AWS EC2 instance

@MrScors

This comment has been minimized.

Copy link

@MrScors MrScors commented Aug 25, 2019

@Izalan Try this: https://stackoverflow.com/a/50403200/8585276

have the same problem but even this didn't help

@ginaocto

This comment has been minimized.

Copy link

@ginaocto ginaocto commented Sep 29, 2019

docker-machine create default --virtualbox-no-vtx-check this might help

Thanks a lot, ur solution worked for me. when 2 days i really confuse to solve this error and u giving me this solution. i really happy for that. TERIMAKASIH @nirvikk

@bhupenkd

This comment has been minimized.

Copy link

@bhupenkd bhupenkd commented Nov 9, 2019

docker-machine create default --virtualbox-no-vtx-check this might help

Thanks a lot, ur solution worked for me. when 2 days i really confuse to solve this error and u giving me this solution. i really happy for that. TERIMAKASIH @nirvikk

This worked for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.