VERR_VMX_MSR_VMXON_DISABLED when starting an image from Oracle virtual box

Asked 18/12, 2013 at 0:40 Answered 5/8, 2020 at 19:48

I'm getting this error while loading a Puppet image from a Oracle virtual box. How can I fix it?

Failed to open a session for the virtual machine learn-puppet-centos-6.4-pe-3.1.0.

VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

In addition, I see that the acellerate-tab in Virtual Box is disabled.

Blanding answered 18/12, 2013 at 0:40 Comment(0)

104

I believe VirtualBox is throwing this error for a number of reasons. Very annoying that it's one error for so many things but, I guess it's the same requirement it's just that the root cause is different.

Potential gotchas:

You haven't enabled VT-x in VirtualBox and it's required for the VM.

To enable: open vbox, click the VM, click Settings..., System->Acceleration->VT-x check box.

You haven't enabled VT-x in BIOS and it's required.

Check your motherboard manual but you basically want to enter your BIOS just after the machine turns on (usually DEL key, F2, F12 etc) and find "Advanced" tag, enter "CPU configuration", then enable "Intel Virtualization Technology".

Your processor doesn't support VT-x (eg a Core i3).

In this case your BIOS and VirtualBox shouldn't allow you to try and enable VT-x (but if they do, you'll likely get a crash in the VM).

Your trying to install or boot a 64 bit guest OS.

I think 64 bit OS requires true CPU pass-through which requires VT-x. (A VM expert can comment on this point).

You are trying to allocate >3GB of RAM to the VM.

Similar to the previous point, this requires: (a) a 64 bit host system; and (b) true hardware pass-through ie VT-x.

So for my little mess around machine that I'm resurrecting that has 8GB RAM but only a ye-olde Core i3, I'm having success if I install: 32 bit version of linux, allocating 2.5GB RAM.

Oh, and wherever I say "VT-x" above, that obviously applies equally to AMD's "AMD-V" virtualization tech.

Hynda answered 7/10, 2014 at 1:35 Comment(8)

Quite a compilation of various reasons I've met for this error, thank you. – Tautomerism 11/10, 2014 at 12:16

Thanks. For me it was because I have added 4 GB. When lowering, the error disappeared. – Ladonnalady 26/10, 2014 at 10:7

For me, I needed to switch from 64bit to 32bit in my virtualbox settings. Then, the error message disappeared. – Photomural 14/1, 2015 at 10:21

I have a 64-bit Windows 8 machine and virtualbox does not give any 64-bit OS versions to choose from. Any ideas? – Monasticism 18/1, 2015 at 22:4

@Monasticism - check points 1, 2 and 3 above. In addition to the host OS requiring 64 bit support, your processor and BIOS need to be correctly configured. – Hynda 29/4, 2015 at 21:51

1a. You have enabled VT-x in the Settings, but it is not available. Try whether you can disable it. – Alumna 20/7, 2015 at 11:7

This also can happen because of to little RAM set for VM – Apteral 13/9, 2015 at 16:56

I had the same problem. I tried to install 64 bit version, when I changed to 32 bit version the problem solved. – Krummhorn 15/9, 2015 at 8:46

That's pretty simple problem to fix as you can see in the error message

You don't have to go with the previous version of virtual box, rather try this

go to your BIOS setting...

inside the virtualization tab enable the virtualiation techniuqe

restart your PC and you will have your Virtual Box up and running.

Unfriendly answered 9/1, 2014 at 6:48 Comment(1)

I went into BIOS (by pressing F2 on start-up), but there is no option named virtualization or even anything related. Apparently this is not an option that all laptops have? Mine is a Lenovo Ideapad 64-bit Windows 8 intel i7-dual core laptop. – Monasticism 18/1, 2015 at 22:7

When I try to set Base Memory around 4000MB (my pc have 8GB) I get the same error 'VT-x is disabled in the BIOS'. But when I reduce Base Memory to 2500MB it works and error is solved.

Antifebrile answered 1/7, 2014 at 19:53 Comment(0)

There is an option in the Virtual Box itself. If you look in the Oracle VM Virtual Box Manager. Select the Virtual Box you want to start. Go to System, the second from above item in the right pane. In System go to the third tab called acceleration. In that tab the first check box is called something like: 'VT-x/AMD-V' (I have the Dutch version, so I don't know the exact string) UNCHECK And then start. That worked for me.

I also got this problem after an upgrade. And I did not have the problem before. But I fail to see the exact connection between the update and the check/unchecking of that option.

By the way, I have no idea where the hell that 'virtualization tab' should be in my 'BIOS'. Maybe I was looking in my PC's BIOS not the System page here which is the BIOS of the VM Machine maybe and that is what you meant Veer7? If it was, it was pretty unclear you meant this. Maybe it's because I have OVM in Dutch not English. But there was nothing called BIOS in the Oracle VM Virtual Box Manager I could find.

Possibility answered 28/1, 2014 at 14:18 Comment(3)

Your method may work on a 32-bit version, but the 64-bit architecture demands the presence of VT-x/AMD-V. The virtualization option has to be enabled in the System-BIOS for it to work correctly. Not very sure where you would find that on a Dutch BIOS ;) – Clamorous 4/5, 2014 at 13:13

on Ubuntu 14.04 6bit helped for 32bit win7. Thank you – Krummhorn 5/6, 2014 at 15:32

This is the correct solution on Ubuntu 14.04 for all types of hosts (Winblows, Linux, etc). Apparently, the "VT-x/AMD-V" option is being inadvertently switched on during the upgrade. – Howdoyoudo 29/7, 2014 at 18:36

I had the same problem. I enabled vtx in bios and it didn't worked. After a doublecheck in the bios I recogniced that the bios said that you have to poweroff (and realy power off) the computer. After that it worked. Heavy Pitfall :)

Chatoyant answered 25/3, 2014 at 14:36 Comment(2)

I'am pretty sure there is a difference between a real shutdown/poweroff and a reboot, somethere at the mainboard level. – Chatoyant 3/5, 2014 at 13:10

This worked for me. I enabled Virtualisation in the bios, but VirtualBox kept telling me that it wasn't enabled. One full and complete shutdown then switch on again worked. – Thrash 6/7, 2014 at 19:3

Just try adjusting ( decrease ) your allotted RAM for the virtual machine in Motherboard in settings. The amount of RAM free in your system at that time might be less than the amount you have allotted for the virtual machine. This worked for me.

Magneto answered 15/12, 2014 at 12:40 Comment(1)

Did the trick here! - I had allocated alot of ram to a VM (amongst other things) and then this error occured - thanks ChiCha – Plausible 23/4, 2015 at 8:4

I have "Intel Virtualization" set to enabled in my BIOS, and I still get this error.

It turns out the problem is that I had Hyper-V enabled in "Windows Features", and apparently VirtualBox and Hyper-V don't play nicely together.

I went to Control Panel -> Windows Features and unchecked Hyper-V. After a reboot, Hyper-V was gone, and I was now able to run my 64-bit VMs again in VirtualBox.

Yoruba answered 23/12, 2014 at 18:34 Comment(0)

Which version VirtualBox do you use? I found the same problem and when use update latest version on my X64 win7 machine VirtualBox-4.3.4-91027-Win But I uninstall it and back to VirtualBox-4.2.18-88781-Win

It works well, try it until Oracle fix it.

Selfassurance answered 18/12, 2013 at 1:15 Comment(0)

That error message also appeared into my VM. First of all, I tried to disable the option "Enable VT-x/AMD-V" (you can find it opening the settings of your VM: Settings->System->Acceleration), there was a warning saying that "Invalid settings detected (you accept the changes and the box was selected again).

Then I read this posts and I tried to enable the Virtualiation Techniuqe (used when you want to enable various VM in your computer (by default is set as Disabled because you don't need that property working.

Dowse answered 9/11, 2014 at 23:25 Comment(0)

If you start a 64 bit virtual machine on a 32 bit host machine you will get this error.

Deloisedelong answered 12/12, 2016 at 7:54 Comment(0)

It happened to me too, and After reading all solutions, I've deleted the created drive and started all over.

The first case (the one that didn't worked) was windows 7 64 bit.

After trying the config as Win 7 32 bit that error didn't appeared again.

Hope this helps someone.

Carchemish answered 23/10, 2014 at 4:5 Comment(0)

I upgraded to Windows 10 x64 (from Windows 7 x64), had a VirtualBox Windows 10 x64 VM, but got the VT-x error. My BIOS was enabled, settings - everything in this post was addressed, but still got the VT-x error.

What fixed it for me was to go to Lenovo and install the latest BIOS for my W550s ThinkPad. Once the upgrade was installed, VirtualBox gave me the x64 options again with no more VT-x errors.

If you are running a W550s, the BIOS version I installed was from September 2015, "BIOS Update Utility" n11uj05w.exe, version 1.10 from the Lenovo website.

Farrica answered 10/11, 2015 at 18:56 Comment(0)

Recently I had this same problem on windows 10 - after installing Hyper-V & other windows features like:

Windows Projected File System, Windows Sandbox, Windows Subsystem for Linux, Work Folders Client,

And it stopped working for me;(

Step uninstall Hyper-V -check if ti stared to work for you - no in my case
Step uninstall other windows features mentioned above! - I worked for me;)

Family answered 5/8, 2020 at 19:48 Comment(0)

Hot tags

Godot Unity Godot Help Programming Godot 4.X GUI GDScript 3D 2D Physics CSharp Godot 3.X VR XR Projects C++

Recommended topics

Hot tags