VERR_VMX_MSR_VMXON_DISABLED when starting an image from Oracle virtual box

Question

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-c         


        

Answer 1

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;(

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

Answer 2

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.

Answer 3

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.

Answer 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.

Answer 5

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:

1. 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.
2. 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".
3. 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).
4. 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).
5. 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.

I hope that helps.

Answer 6

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