Date: | July 17, 2018 / year-entry #163 |
Tags: | tipssupport |
Orig Link: | https://blogs.msdn.microsoft.com/oldnewthing/20180717-00/?p=99265 |
Comments: | 7 |
Summary: | That's where your virtual machine resource usage goes. |
Say you're minding your own business and you discover that
this process called
The If you want to make it stop, shut down your virtual machines. Bonus chatter: Strictly speaking, what it actually represents is the resources of the other virtual machines, since Windows itself is running in a virtual machine under the hypervisor. You may not be explicitly using the hypervisor, but some other features are built on top of the hypervisor. |
Comments (7)
Comments are closed. |
You mean Hyper-V virtual machines, right?
I believe you are right. The bonus chatter hints about a bare-metal hypervisor. Hyper-V is the only one Microsoft has ever made. And since a Microsoft employee has written this, it is definitely about a Microsoft product. (Bonus chatter: This principle does not always hold about other company employees, even those whose competing products sell much stronger than Microsoft’s.)
I suppose there’s no point killing vmmem.
That would be like killing the “Idle cpu time” process
As I can see in host’s task manager, CPU usage is assigned to vmmem, but RAM consumption is assigned to vmwp.exe. It doesn’t make sense for me. Why two processes per VM? One would be ideal, no?
VMWP.EXE is a real process.
On my machine, I see a vmmem process consuming lots of memory (1.4GB private bytes, 350MB working set), but I have no Hyper-V machines running. The process runs as “NT VIRTUAL MACHINE\{some guid}” user. I even deleted all my Hyper-V machines – still vmmem remains.
I presume it’s some implicit VM, like Windows Defender Application Guard uses to run Edge (and office?) – how can I determine that?