Hi,
This article shound answer most.
Hyper-V Dynamic Memory Configuration Guide
Hyper-V
running on Windows Server 2012 and Windows Server 2012 R2 automatically calculates an amount of memory to reserve for exclusive use by the management host operating system. This memory is used to run virtualization services. If the computer
is part of a failover cluster, Hyper-V also reserves enough memory to run failover cluster services. In previous versions of Hyper-V you might have needed to modify the
MemoryReserve registry setting to ensure adequate memory for these functions. This is no longer necessary for Hyper-V running on Windows Server 2012 and Windows Server 2012 R2.
The Min,Max RAM setting should be more aligned to the VM requirements, rather than the Host. Certain Applications, like Exchange Server recommends not to use it.
The reason you see different values are due to the load and demand pattern raised by the VM, the host will automatically adjust the value depending on the requirement calculations done by it.
So the current Memory Demand can be 4132, but it could be the next second its asking for 7k.
Assigned Memory = 7380 works in that case.
While dynamic memory allows Hyper-V to
add memory to a virtual machine in just a few seconds (and sometimes under a second) there is still a window of time between when a virtual machine needs memory and when Hyper-V can add memory.
In case you think its not working, setup counters to
monitor the behaviour to see if its not working or working.
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.
