Dynamic Memory allocation in a Virtual Machine does not change although there is available memory on the host

A virtual machine hosted on a Windows Server 2008 R2 SP1 Hyper-V server with Dynamic Memory configured may indicate a 'Low' or 'Warning' Memory Status in the Hyper-V Management snap-in. Additionally, there is available memory on the host which can be quickly verified by opening Task Manager in the Parent partition. With Task Manager open, select the Performance tab, and then Click the Resource Monitor button at the bottom of the interface. With Resource Monitor open, Select the Memory tab. The display will indicate how memory is being used in the Parent Partition. Open Event Viewer and verify that an Event ID 3322 is registered in the Microsoft-Windows-Hyper-V Worker/Admin log. The event message indicates additional memory cannot be allocated to the virtual machine because there is not enough free disk space to extend the memory contents file.

Event ID: 3322
Source: Hyper-V-Worker
Level: Error
Description: <Virtual Machine name>: Cannot allocate more memory to the virtual machine because there is not enough free disk space to extend the memory contents file '<path to virtual machine .bin file' to <memory value>. (Virtual machine ID <VM GUID>). To free up disk space, delete unnecessary files from the disk and try again. 

Note: The *.bin file contains the virtual machine or snapshot memory contents. When dynamic memory is configured for a virtual machine, the size of this file can increase based on the memory configuration settings implemented by a user for that VM or the memory demand inside the virtual machine itself. 

There are two possible causes for this:

1. Disk space may not be available on the disk supporting the *.bin file.
2. In a Hyper-V Failover Cluster, a virtual machine can have its configuration information stored on cluster shared storage (a Physical disk resource or a Cluster Shared Volume (CSV). If the physical disk resource or the Cluster Shared Volume (CSV) goes Offline or Fails, the VM placed in a critical state. Once the storage is re-connected, the VM should no longer be in a critical state. However, virtual machine worker process (vmwp.exe) does not refresh all of its file handles. 
   

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.