The DM feature provides a feedback loop for managing the guest memory dynamically between the min memory and the max memory. If the memory pressure is low, the host will drain the memory out of the guest - the floor on what will be left in the guest is the min memory. It is likely that the host was actively reducing the memory assigned to the guest and there was sudden burst of pressure. Perhaps increasing the min memory would help you case. K. Y > -----Original Message----- > From: Jon Stanley <jonstanley@xxxxxxxxx> > Sent: Monday, January 25, 2021 1:07 PM > To: KY Srinivasan <kys@xxxxxxxxxxxxx> > Cc: Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>; Stephen Hemminger > <sthemmin@xxxxxxxxxxxxx>; wei.liu@xxxxxxxxxx; linux- > hyperv@xxxxxxxxxxxxxxx > Subject: Re: [EXTERNAL] hv_balloon issues?? > > On Mon, Jan 25, 2021 at 3:51 PM KY Srinivasan <kys@xxxxxxxxxxxxx> wrote: > > > > I take it that this is on Windows Server machine. What are the Dynamic > memory settings for the VM under question. > > No, sorry for leaving that out. This is on Windows 10 Pro for Workstations, on a > Xeon W-2155 machine with 192GB RAM. Apologies but I'm more of a Linux guy > than Windows :). If I've gotten the wrong thing let me know, > > PS C:\Users\jonst> Get-VM -VMName build-test2 |Format-List * <snip> > CPUUsage : 0 > MemoryAssigned : 6036652032 > MemoryDemand : 5130682368 > MemoryStatus : OK > NumaAligned : False > <snip> > DynamicMemoryEnabled : True > MemoryMaximum : 1099511627776 > MemoryMinimum : 536870912
