VT-x error when setting up VirtualBox on Ubuntu

23

I have tried to setup VirtualBox on Ubuntu, but I get this error even though Intel virtualization technology (VT-x) is set to Yes in the BIOS:

Failed to open a session for the virtual machine Ubuntu.

VT-x is disabled in the BIOS for both all CPU modes > (VERR_VMX_MSR_ALL_VMX_DISABLED).

Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

EDIT: according to SecurAble my system is able to handle virtualization:

Securable screenshot

ubuntu
virtualbox
vt-x
asked on Super User Aug 14, 2015 by user2676140 • edited Aug 14, 2015 by mguassa

4 Answers

40

What solved my issue was using less than 3 GB of ram in the virtual box session. I was originally attempting to utilize roughly 6 GB.

You are trying to allocate >3GB of RAM to the VM. This requires: (a) a 64 bit host system; and (b) true hardware pass-through ie VT-x.

answered on Super User Aug 14, 2015 by user2676140 • edited Aug 14, 2015 by user2676140
3

In my case Memory(RAM) was not a problem, just VT-x wasn't enabled in BIOS. Or in some cases, CPU may not have support of VT at all.

To check whether your CPU supports it or not. try:

sudo apt-get install cpu-checker
sudo kvm-ok 

Second command will output if VT is enabled or not or if it's available at all.

If it does, go to BIOS and enable it. It should be named Intel Virtualization Technology, Intel VT-x, Virtualization Extensions, Vanderpool, or something similar.

answered on Super User Jul 29, 2016 by notgiorgi
1

My error was VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Solution is you should switch on the virtualization in the bios of the host operating system(i my case it is windows)

answered on Super User Apr 12, 2017 by Thousif Ameer khan
0

I've been dealing with this issue for a few hours, trying to solve it with probably all the answers I could find on the Internet.

What have worked for me was removing Hyper-V role from my Windows...

MJ

answered on Super User Jul 7, 2016 by MichaelJ

User contributions licensed under CC BY-SA 3.0