TONYSO

Tonyso Credo: "Look for a pattern, and solve it for everything"

Hyper-V How To: Troubleshoot Event ID: 3112-Hypervisor Operation

Hyper-V How To: Troubleshoot Event ID: 3112-Hypervisor Operation

  • Comments 1
  • Likes

The new Health Model pages are now live. Some of you seem to be having trouble with Event ID: 3112 with error message that starts “The virtual machine could not be started because the hypervisor is not running.”

Check Hyper-V status

The virtual machine could not be started because the hypervisor is not running. Check your BIOS settings and BCD store, then restart the physical computer.

Hyper-V requires hardware support, including: an x64 CPU; VT (Intel) or AMD-V (AMD) hardware extensions; No eXecute (NX)/eXecute Disable (XD) and full BIOS support for hardware virtualization. Check your physical computer's BIOS settings to ensure that virtualization features are enabled, and then turn off the power to your physical computer. Restart the physical machine. NOTE: Restarting the physical computer is not sufficient.

You can use the Virtualization Detect (DetectVp.EXE) tool to check if the physical computer meets the requirements for Microsoft virtualization software. This test checks virtualization support for both Intel and AMD processors. The tool is part of the Windows Driver Kit (WDK).

To download the WDK .iso file:

1 - Go to the Microsoft Connect Web site at http://go.microsoft.com/fwlink/?LinkID=100623 and sign in with your Live ID.

2 - Enter the Microsoft Connect Web site. Click Connection Directory.

3 - Click Developer Tools, and then click "Windows Driver Kit (WDK), Windows Logo Kit (WLK) and Windows Driver Framework (WDF)."

4 - Click the Download link to download 6.1.6001.18002.081017-1400_wdksp-WDK18002SP_EN_DVD.iso

Check that Boot Configuration Data (BCD) store is set to start the hypervisor, and then restart your physical computer.

The BCD store contains boot configuration parameters and controls how the operating system is started in Windows Vista and Windows Server 2008 operating systems. These parameters were previously in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile RAM (NVRAM) entries (in Extensible Firmware Interface-based operating systems).

You can use the Bcdedit.exe command-line tool to update BCD store with the correct launch options as referenced in the error, and then restart the server. Bcdedit.exe is located in the \Windows\System32 directory by default.

Note: Administrative privileges are required to use bcdedit to modify the BCD store. Unless otherwise specified, bcdedit operates on the system store by default.

On PC/AT BIOS systems, the BCD store resides in the active partition's \boot folder. On EFI systems, the file is located on the EFI system partition (ESP) under \EFI\Microsoft\Boot.

Caution:  The BCD data store is a registry hive, but that hive should not be accessed with the registry API. Interaction with the underlying firmware occurs in the supported BCD interfaces. For this reason, BCD stores should be accessed only through the associated tools or WMI API. Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

For further information on using Bcdedit.exe, see http://go.microsoft.com/fwlink/?LinkID=147513

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment