[Win] Oracle VirtualBox: Workaround For Initialization Issue

“and first for something complete different”: Muzaq… coding or administrating system can’t do without gooood muzaq. Check our latest tunes here :-)

History

VirtualBox is an open source virtualization software. Originally it has been developed by a german company named Innotek, which has been acquired by SUN Microsystems in 2008. SUN Microsystems in turn has been acquired by ORACLE in 2010.

Innotek originally collaborated with Connectix on Virtual PC – a virtualization software targeting the Mac OS platform. Connectix has been bought by Microsoft in 2003. Innotek then decided to develop VirtualBox.

Status Quo

VirtualBox is used by many companies for virtualization and thus developing. Palm for example uses VirtualBox for WebOS development in an emulated environment. Thus allowing either Linux, Mac OS or Windows host systems for development.

CPU VT-X/AMD-V Issue

After configuring a dual core virtual machine and trying to start you may encounter a message box indicating:

VERR_VMX_MSR_LOCKED_OR_DISABLED

This issue may occur no matter which host operating system you’re using. The reason for this might be:

  • you’re not using a CPU that supports hardware virtualization
  • your BIOS does not support hardware virtualization properly
  • hardware virtualization is disabled in your BIOS settings (check it!)
  • there is a bug in your current BIOS version regarding

Known Workarounds

  • Disable USB for the virtual machine
  • Reduce the amount of CPU cores to 1
  • upgrade your BIOS to the latest version (this might be dangerous)
  • Disable VT-X/AMD-V
  • Disable 3D acceleration
  • Shutdown your host machine, unplug (!) from electricity for say 30 secs, reboot then

As we’re currently using VirtualBox only on the Windows XP platform we categorized this article under Win, anyway it is very likely that the same issue also occurs under Linux or Mac OS, as VirtualBox on all platforms derives from the same source code.

Any suggestions, hints or things need to be added? Don’t hesitate to tell us below…

You can leave a response, or trackback from your own site.

9 Responses to “[Win] Oracle VirtualBox: Workaround For Initialization Issue”

  1. Phlip says:

    u suck. I just got a Lenovo Y560 15.6″ notebook featuring Intel Core i7-720QM Processor with 4GB memory and 500GB hard drive

    specifically because it has 8 hardware threads! Now I can only use 1 of them

  2. Ean says:

    Disable VT-X/AMD-V sorted it for me! Thanks very much, I was about to send this F—ing lenovo and windows “ultimate” 7 back for a refund!

  3. Russ says:

    yes, disable VT-X/AMD-V and problem goes away on windows-7. Thank you so much.

  4. [...] Read in 12 months… 7035x [Win] Oracle VirtualBox: Workaround For Initialization Issue 5383x [MacOS] VirtualBox 3.2 To Support Mac OS Guest on Windows Host [Update] 3696x [Media] [...]

  5. Sidharam says:

    Hi, I reduced the CPU cores from 4 to 1 and disableD VT-X/AMD without shutdown the host system, just stared my Win XP working but performace is very low…

  6. Miel says:

    Reducing the cpu cores from 2 to 1 fixed it for me! Thanks a lot for this entry!

  7. Suren says:

    I did the above steps now my VM is starting but it does not load windows… It keeps on restarting once the windows files are loaded…

  8. David Singleton says:

    I have just had the same error message just after I had upgraded the BIOS for my ASUS Z77 motherboard. I therefore checked the BIOS settings and found that the new BIOS had turned Intel Virtualisation off! I turned Intel Virtualisation on – and – low and behold – VirtualBox worked once more without problems.

  9. mtcommy says:

    Thanks for the post – the last workaround:
    “Shutdown your host machine, unplug (!) from electricity for say 30 secs, reboot then”
    worked for me (but why? ;)).
    My mainboard is ABIT IP35 (newest BIOS) and CPU is Intel Core 2 Quad Q9300.

Leave a Reply