The VM Health Event monitor tracks the following virtual machine statuses:
Virtual Machine Statuses
P2V Creation Failed
V2V Creation Failed
Host Not Responding
Critical/Error Health State (Red):
Virtual Machine Status
The virtual machine was not created successfully. To find out which step in the job failed, view job details in Jobs view of the VMM console. The job failure error code gives the reason for job failure. For more information, see Monitoring Jobs (http://go.microsoft.com/fwlink/?LinkId=268264) in VMM 2016 Help.
View troubleshooting for virtual machine statuses at http://go.microsoft.com/fwlink/?LinkId=268228 .
Possible causes include:
Insufficient disk space on the host or library server.
Insufficient memory on the host or library server.
Communication failure between the VMM management server and the host or library server.
Objects required for virtual machine creation are in use and were locked by another process.
The virtual network that the virtual machine’s network adapter is attached to is not configured on the host.
A virtual DVD on the virtual machine is configured to attach to a drive that does not exist on the host.
A temporary spike in resource usage on the host because multiple virtual machines are being created or deployed on the host caused the update to fail.
This can occur when customization fails due to a time out while waiting for the virtual machine to boot (at the start of customization) or power off (after customization).
An incorrect operating system version is specified for the virtual machine.
A custom unattend.xml has invalid entries.
The virtual machine took too long to boot or shutdown due to insufficient resources, such as memory or CPU.
There was a problem with the domain join, such as an invalid password or network connectivity problems.
The product key is invalid.
For additional troubleshooting information, look at the log files in %systemdrive%\Windows\Panther\. View troubleshooting for virtual machine statuses at http://go.microsoft.com/fwlink/?LinkId=121829.
The migration of the virtual machine from one host to another or from a host to a library server failed.
Insufficient disk space on the host.
Insufficient memory on the host.
Destination host already has a virtual machine with the same name.
A temporary spike in resource usage on the host because multiple virtual machines are being created on or deployed on the host.
During an automatic placement (virtual machine self-service or drag and drop placement), no default virtual machine path was configured on the preferred volume on the host.
A SAN transfer failed because of a Virtual Disk Service (VDS) error on the source or destination computer. This failure might be caused by a transient VDS error.
Windows Firewall is enabled on the destination server, and no firewall exception has been added for the BITS port.
The Virtual Server Run As account for the virtual machine does not have network credentials.
View troubleshooting for virtual machine statuses at http://go.microsoft.com/fwlink/?LinkId=121829.
Virtual Machine Manager is unable to find the virtual machine.
The virtual machine’s host is in a server cluster, and the virtual machine failed over to a different host. If the virtual machine's current host is now managed by VMM, the virtual machine will return to a healthy state after the next refresh.
The Virtual Machine Manager agent and the Virtual Server service on the host do not have sufficient permissions. Both services must have Full Access to the virtual machine.
An administrator moved the virtual machine’s configuration files to a different host manually without registering or updating the virtual machine in Hyper-V or Virtual Server.
An administrator moved the configuration files for a stored virtual machine within a library share or to a different library share manually without refreshing the source and destination library shares in VMM. Therefore, the virtual machine path has not been updated in the VMM database.
The virtual machine configuration file (.vmc) is corrupted.
The virtual machine was deleted from Hyper-V, Virtual Server, or VMware ESX Server without removing the virtual machine from VMM.
The virtual machine has unsupported undo disks that were created in Virtual Server. Before you can manage the virtual machine in VMM, you must discard or merge the undo disks.
To resolve this issue, use the Disable undo disks action in Virtual Machines view of the VMM console. For more information, see How to Disable Undo Disks for a Virtual Machine (http://go.microsoft.com/fwlink/?LinkId=121821) in VMM 2008 R2 Help.
Resolutions for statuses that cause a critical or warning health status for this monitor are very dependent on the error or job failure that occurred.
For detailed troubleshooting information for each critical and warning status for a virtual machine, see the following topics in the VMM TechNet Library (http://go.microsoft.com/fwlink/?LinkId=102009):
Troubleshooting Virtual Machine Statuses (http://go.microsoft.com/fwlink/?LinkId=121829)
Troubleshooting “Not Responding” Status for a Virtual Machine Host (http://go.microsoft.com/fwlink/?LinkId=121830)