Home > Oracle, VirtualBox > VirtualBox solved VERR_VMX_MSR_LOCKED_OR_DISABLED

VirtualBox solved VERR_VMX_MSR_LOCKED_OR_DISABLED

VirtualBox Manager VERR_VMX_MSR_LOCKED_OR_DISABLEDWhile creating a Ubuntu 12.10 machine VirtualBox I ran into an error – VirtualBox VERR_VMX_MSR_LOCKED_OR_DISABLED – on my company issued HP ProBook. This halts the startup process of the virtual machine. You won’t be able to use it.

Here is the complete log and a screenshot:


Failed to open a session for the virtual machine Ubuntu 12.10.

VT-x features locked or unavailable in MSR. (VERR_VMX_MSR_LOCKED_OR_DISABLED).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

I remembered that there were issue were issues with HP bios from the VirtualBox FAQ using ENABLE VT-X/AMD-V:

some HP BIOSES have a glitch, When You ENABLE VT-X/AMD-V, You DISABLE it, so do try both ways.

VirtualBox Enable VT-x AMD-VSo the first solution I tried was to uncheck the box to ENABLE VT-X/AMD-V. That solved my problem. Now VirtualBox was able to start my Ubuntu machine. Check the screenshot how to disable (or enable the) VT-X/AMD-V setting.

Yep, I know this is against the advice I gave to improve VirtualBox performance. However I need it on this hardware to get my machines running…

Categories: Oracle, VirtualBox
Tags: ,
  1. josh
    June 25th, 2013 at 16:11 | #1

    I can confirm that this works on a newer (2012) HP

  2. Fabien
    July 11th, 2013 at 10:46 | #2

    I can confirm this too

  3. diman
    August 20th, 2013 at 09:20 | #3

    I fix same error by set only one processor at the VM settings

  4. Tilda Gagnon
    November 12th, 2013 at 02:54 | #4

    You saved my life! It is working!

  5. rfariya
    December 7th, 2013 at 16:41 | #5

    Hi.
    I had the same problem, but even with enabling the virtualization Technology in my BAIOS it didn’t work and it gave me the same error. After a bit searching I figured out that it is a bug in hp Baios and you should not just restart your system, but do completely shutdown and then it would work.

  6. seshu
    February 13th, 2014 at 12:15 | #6

    The amount of memory allocated to these VMs is also uncomfortably close to the total amount of available memory in the host (4.3GB available, 4GB allocated as RAM, more as VRAM). In an ideal world your VM should not use more than half the available host memory, otherwise wierd intermittent problems are the likely result. Descrese VM RAM to less than half physical RAM memory.

  1. February 22nd, 2013 at 15:06 | #1