Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 3112 Source: Microsoft-Windows-Hyper-V-Worker

Level
Description
The virtual machine could not be started because the hypervisor is not running. The following actions may help you resolve the problem:

1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.

2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting you must turn off the power to the physical computer and then turn it back on. Resetting the physical computer is not sufficient.)

3) If you have made changes to the Boot Configuration Data store review these changes to ensure that the hypervisor is configured to launch automatically.
Comments
 
Check if these settings are enabled in system Bios:
Intel VT = Enabled
No Execute Memory Protection = Enabled

If any of these are in a disabled state, Hypervisor would not start the Virtual machine.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...