FocIS
asked on
How can I see what is using all the ram on a server
We have a server 2008 r2 x64 box which is intended to be logged into by users using remote desktop from their workstations.
The 2008 r2 server is one of three hyper-v vm's which are hosted on a much more powerful server (server 2012 with 64gb ram)
the 2008 r2 vm does not run sql or exchange or any other typical resource hog... just microsoft office 2013. It also doesn't host files.
With no users logged in, no obvious programs running, just after a reboot, all 31gb is being used by something. Whatever it is doesn't apparently show up in task manager or resource monitor. 0% cpu, 0% network, 0% disk... 99% memory.
How can i find out specifically what is using all this memory? The server is almost unusable in the current state.
Attached are some diagnostic pictures
shot1.jpg
shot2.png
shot3.jpg
The 2008 r2 server is one of three hyper-v vm's which are hosted on a much more powerful server (server 2012 with 64gb ram)
the 2008 r2 vm does not run sql or exchange or any other typical resource hog... just microsoft office 2013. It also doesn't host files.
With no users logged in, no obvious programs running, just after a reboot, all 31gb is being used by something. Whatever it is doesn't apparently show up in task manager or resource monitor. 0% cpu, 0% network, 0% disk... 99% memory.
How can i find out specifically what is using all this memory? The server is almost unusable in the current state.
Attached are some diagnostic pictures
shot1.jpg
shot2.png
shot3.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
According to MS support, this is the way Hyper-V Dynamic Memory works.
http://blog.luxem.org/2013
If you shutdown the guest and uncheck Dynamic Memory from the guest memory properties it should return to some normal state.
Leon
http://blog.luxem.org/2013
If you shutdown the guest and uncheck Dynamic Memory from the guest memory properties it should return to some normal state.
Leon
ASKER
Quick and to the point, exactly what i needed - thanks!
ASKER
Disabling dynamic memory did fix it - it's a shame dynamic memory didnt work, but, we have plenty enough to go around so fixing it at 32gb is fine
glad I could help :)
ASKER
it shows 29gb in "Driver Locked"
now to find out what driver locked up all that ram - wow
shot4.png