A. For each VM (guest) running on Hyper-V, a VM Worker Process (vmwp.exe) is created by the Virtual Machine Management Service (vmms.exe). This process manages the VM, but each of these processes is just called vmwp.exe and it's not obvious which vmwp.exe process is for which VM.
Fortunately, you can use the Sysinternals Process Explorer tool and look at each of the vmwp.exe processes. In the Image tab, the command line that was used to start the process is shown, including the GUID of the VM, as shown here.
 |
Click to expand. |
You can then match this GUID to the GUID of the VM. You can easily see the GUID of a VM by looking at the name of the XML configuration file for the VM, named
Knowing which vmwp.exe relates to each VM can be very useful if you have a VM that won't stop and need to kill the vmwp.exe process for that VM.
Related Reading:- Q. What are Virtual Machine Queue (VMQ) and VM-Chimney in Hyper-V R2?
- Free Virtualization Platforms
- Q. The output from Get-WindowsFeature doesn't help me. How can I query whether a role or feature is installed?
- Q. Should I back up at the Hyper-V host level or within my guest OSs?
Check out hundreds more useful Q&As like this in John Savill's FAQ for Windows. Also, watch instructional videos made by John at ITTV.net.
