Virtual machine that's running on Windows Server 2012 R2 doesn't start
Not enough memory in the system to start the virtual machine '<Virtual Machine Name>'
Also, the following event is logged in the Microsoft-Windows-Hyper-V-VMMS-Admin log.
Event ID: 19544
Failed to start the virtual machine 'Virtual Machine Name' which required xxxx MB of memory because only xxxx MB was available in the system (Virtual machine ID <Virtual Machine ID>).
The remaining memory is available to virtual machines. However, this quantity differs from what is displayed in Task Manager as “available memory.” Therefore, the virtual machine may not start even if the Hyper-V host appears to have sufficient memory according to Task Manager.
To accurately check the available memory for virtual machines, see the "Workaround" section to use the performance object and counter name.
The following performance counter can be used to explicitly check how much memory is available for virtual machines:
- The instance name is "System Balancer."
- The Hyper-V Dynamic Memory Balancer\Available Memory value depends on the amount of memory that's used by the application installed in the Hyper-V host, and the amount that's used by vmwp.exe.
Article ID: 2962295 - Last Review: 02/29/2016 18:44:00 - Revision: 6.0
- kbexpertiseadvanced kbsurveynew kbtshoot KB2962295