Use Hyper-V Logs for Troubleshooting Guide
Let's take a look at troubleshooting Hyper-V with event logs and see how this troubleshooting tool can be used to identify problems.
An Overview of Hyper-V Log
Hyper-V has changed over the last few years and so has our event log structure. This post gives a short overview on the different Windows event log channels that Hyper-V uses. It can be used as a reference to better understand which event channels might be relevant for different purposes.
As a general guidance you should start with the Hyper-V-VMMS and Hyper-V-Worker event channels when analyzing a failure. For migration-related events it makes sense to look at the event logs both on the source and destination node.
Hyper-V event log channels
There are different log files that are used to capture Hyper-V information in typical event viewer fashion.
To find the various Hyper-V events logs in the Windows Event Viewer, navigate to Windows Logs > Applications and Services Logs > Microsoft > Windows.
Windows Server 2016 contains the following log file groupings to help with troubleshooting Hyper-V environments:
- Hyper-V-Compute – Captures information regarding the container management API known as the Host Compute Service (HCS) and serves as a low-level management API
- Hyper-V-Config – Captures events related to the virtual machine configuration files. Errors that involve virtual machine configuration files either missing, corrupt, or otherwise inaccessible will be logged here
- Hyper-V-Guest-Drivers – Log file that contains information regarding the Hyper-V integration services components and provides valuable information in regards to troubleshooting issues with the integration components
- Hyper-V-High-Availability – Events related to Hyper-V Windows Server Failover Clusters
- Hyper-V-Hypervisor – Events related to the Hyper-V hypervisor itself. If Hyper-V fails to start, look here. Also, informational messages such as Hyper-V partitions created or deleted will be logged here
- Hyper-V-Shared-VHDX – Information specific to shared VHDX virtual disks between virtual machines are found in this log
- Hyper-V-StorageVSP – Captures information regarding the Storage Virtualization Service Provider. This contains low-level troubleshooting information for virtual machine storage
- Hyper-V-VID – Logs events from the Virtualization Infrastructure Driver regarding memory assignment, dynamic memory, or changing static memory with a running virtual machine
- Hyper-V-VMMS – Virtual Machine Management Service events which are valuable in troubleshooting a virtual machine that won’t start or a failed Live Migration operation
- Hyper-V-VmSwitch – Contains events from the virtual network switches
- Hyper-V-Worker – the log that captures Hyper-V worker process information which is responsible for the actual running of the virtual machine
If you would like to collect events from these channels and consolidate them into a single file, you could use the HyperVLogs PowerShell module to enable all the important Windows event channels into a single evtx file, which help with piecing together issues or troubleshooting an underlying problem.
Best free way to protect Hyper-V Virtual Machine
For enterprise or users who own multiple VMs running important business, Hyper-V backup is a necessary step in case of various possible threats and errors.
Here, I’d like to introduce a FREE Hyper-V backup solution - AOMEI Cyber Backup. It is a powerful backup software to protect Hyper-V virtual machines automatically and reduce business risk. With this efficient tool, you can enjoy the following features for free:
✤ Multiple Storage Destinations: backup to local or network share destinations.
✤ Automated Execution: automate unattended virtual machine protection and notify via email.
✤ Perpetual Free: you can use AOMEI Cyber Backup Free Edition with no time limit.
✤ Easy-to-use: Backup virtual machine with flexible backup strategies based on a few clicks.
✤ Hot Backup: Backup entire Hyper-V virtual machines while running including OS, configuration, application, personal data and system state.
✤ Restore from Any Point: Restore entire VM from any backed-up history versions with a few clicks.
Download and enjoy the perpetual free edition:
*You can choose to install this VM backup software on either Windows or Linux system.
How to back up Hyper-V VMs step by step
1. Launch AOMEI Cyber Backup and bind your Hyper-V device.
2. Click Create New Task to set up the backup task as you need.
- Device Name: select one or more virtual machines for backup.
- Target: Enter a network or local path to specify the backup location.
- Schedule: Set up the backup task with full/incremental backup and select the time to run each backup automatically.
3. Click Restore to recover your virtual machine rapidly when necessary. In the restore wizard, you can restore any VM in the backup task from any backed up history versions.
While the Free Edition can cover most of Hyper-V backup needs, you can also upgrade to enjoy:
✦ Batch VM backup: Batch backup large numbers of VMs managed by hosts.
✦ Backup cleanup: Configure retention policies to delete unwanted old backup files automatically, and therefore save your storage space.
✦ Restore to new location: Easily make a clone of the VM in the same or another datastore/host, saves the trouble to reinstall and configure the new VM.
Summary
Microsoft does a better job of specifically capturing Hyper-V events and organizing Hyper-V specific logs, which allows administrators to utilize Hyper-V logs to troubleshoot the Hyper-V environment when problems arise.
With each of the major Hyper-V components being logged, administrators can pinpoint the nature of a specific Hyper-V error.