0
  • Intel Core i5 7400 (processor)
  • Odense2-K (motherboard)

I'm trying to spin up an instance of MacOS Sierra inside my Windows 10 machine using VirtualBox. When I start the machine, I get this error message:

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

A quick google search tells me that I do not have hardware virtualization enabled on my machine. I can access the UEFI firmware settings, but I did not see any options there for enabling virtualization. How can I turn on VT-x?

My BIOS settings

BIOS 1

BIOS 2

2
  • @Biswa Hello. This is actually the exact article I followed before this post. From my BIOS settings I do not see any virtualization options.
    – smilebomb
    Sep 12 '17 at 3:24
  • Here is the option I find: go to bios settings > open Security tab > System Security > Virtualization Technology
    – Biswapriyo
    Sep 12 '17 at 17:23
1

First, you may want to read the following page, which describes where the relevant options are set on some computers:

http://www.thomas-krenn.com/en/wiki/Activating_the_Intel_VT_Virtualization_Feature

If that doesn't help, one (perhaps long-shot) approach may be to use my rEFInd boot manager to boot the host OS (Windows for you):

  1. Verify that you've got an Intel CPU. (I know your topic says you do. I'm putting this step here mainly so that somebody else with a similar problem and an AMD CPU doesn't try this feature, which might do weird things on an AMD-based computer.)
  2. Download the USB flash drive version of rEFInd from its downloads page.
  3. Write the rEFInd image to a USB flash drive, as described in the documentation.
  4. Edit EFI\BOOT\refind.conf on the USB drive: Uncomment the enable_and_lock_vmx option and set it to true. (Note that the flash drive image has a single EFI System Partition. I'm not sure offhand if Windows will mount that by default. If not, you might need to change its type code, use Linux, or otherwise jump through hoops to access that filesystem.)
  5. Reboot to the USB drive and hope for the best. rEFInd should appear and enable you to boot Windows. With any luck, VirtualBox will now work.
  6. If VirtualBox now works, you can install rEFInd to your hard disk, as described in its documentation. Unfortunately, this is more difficult in Windows than in Linux, but it can be done. After installing rEFInd, be sure to edit EFI\refind\refind.conf on the hard disk's ESP. You might also want to adjust the timeout line to have rEFInd boot Windows immediately rather than present its menu.

The enable_and_lock_vmx option was added to rEFInd for the benefit of Mac users who want to use Hyper-V; however, it sounds like it might work for you, too. I've never tested it for your use case, though. (In fact, I've barely tested it at all; the relevant code was a submission from somebody else.)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.