How to fix event ID 3112 “The virtual machine could not be started because the hypervisor is not running.”?


1. Check if your CPU supports virtualization technology . Download CPU-Z and check instructions list for Intel VT-X or AMD-V.

Image
AMD-V on AMD Turion
Image
Intel-VTx

2. Check if virtualization enabled on your CPU (CPU Configuration, BIOS). For example, on Intel Sr1670HV Intel Virtualization Tech and Execute-Disable Bit Capability must be enabled. Usually, you have to just find settings (in CPU Configuration) that contains “Virtualization” or “Execution” and enable them.

Image

3. I had a problem with enabling hypervisor on my server and both (1,2) steps did not help me.Before it I have had an issue with OS loading, so I repared my server using bootrec.exe utility (/rebuildbcd and /fixboot parameters).  According with http://msdn.microsoft.com/en-us/library/windows/hardware/ff542202(v=vs.85).aspx I checked my bcdedit (just type it into cmd) for the following parameter and noticed there were no one:

hypervisorlaunchtype [ Off | Auto ]

Controls the hypervisor launch options. If you are setting up a debugger to debug Hyper-V on a target computer, set this option to Auto on the target computer.

I solved it by running bcdedit /set hypervisorlaunchtype auto. Restarted server and successfully started my VMs.

Image

2 thoughts on “How to fix event ID 3112 “The virtual machine could not be started because the hypervisor is not running.”?”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s