Bro this you check the HyperV Best Practices????
There is some info about configure AV exclusions for hyperv check if you have it......
My understanding is that we have not seen the issue on the actual Hyper-V VM's themselves, its just on hosts. I have checked on a couple of our stand alone servers, and they appear fine, as do all the workstations.
We have a host server in each school that runs four or five VM's on a single host. We have different manufacturers of host with the same issue, so its unlikely to be hardware, but at this stage its still a bit cloudy.
What went wrong here was that we did not deploy to one host first using the Eva branch .....
I just wanted to say that we too have experienced this issue. In our case it is on a 5.1u3 ESXI enviroment. It has primarily been an issue with Server 2003 systems that have a lower memory cap for loaded drivers. Eventually 2008r2 systems are affected as well, but it takes much longer.
We localized the issue to Access Protection. Disabling access protection caused the memory to stop iterating higher. It doesn't matter what options are use (even none), if AP is on, the memory eventually runs out.
We had submitted a sample in an SR over a month ago and they were unable to find anything. Figured we were too ahead of the curve and have been monitoring since then waiting for others to verify the issue (that it wasn't unique to us).
did you experience this issue with standalone servers outside 5.1u3 ESXI environment? and how can you tell if there is a memory leak? do you watch vshield.exe memory usage?
We don't have any physical 2003 systems anymore, and we disabled AP when the issue was discovered (it had only hit a couple of non-2003 systems by that point, but we verified it on a 2012 system).
We used poolmon to verify. The MFeB would continue to iterate higher and higher before eventually overloading the non-paged memory pool. On Server 2003 systems this is only around 256 MB, so it fills quick. On 2008 and above this number is significantly higher (higher enough that systems with monthly patching might not hit it).
Basically, if I turn on access protection, the MFeB will start iterating higher.
Do you mean windows 2012 r2 and windows 2008 r2 are affected by the memory leak? if a system has this issue , should it report it as pool non-paged bytes event on windows event log?
From what we saw, all versions of Server we use (2003, 2008/08r2, 2012r2) are affected by it, however it is only crippling on 2003 systems or systems that are rebooted infrequently. We did see non-paged events in event log which led to checking poolmon.