I'm running a Virtual Machine server on Hyper-V that stalls about once a week, effectively rendering certain services it is running to be useless.
-The physical host machine
- CPU: 6-core Xeon E5-2620 2.10GHz
- RAM: 16GB
- OS: Windows Server 2008 R2
- Services
- File Services
- Hyper-V
-The Virtual Machine
- Processor
- Logical Processors: 4
- Virtual Machine Limit: 100
- Relative Weight: 100
- Memory (Dynamic)
- Memory Buffer: 20%
- Memory Weight: High
- Network Adapter: The only VM on this Virtual Network assigned to its own port
- OS: Windows Server 2008 R2
- Services
- File Services
- Print and Document Services
- Web Server (IIS)
- Windows Server Update Services
Here are the symptoms:
-When the server stalls I can...
- Ping the server
- Query the server using PowerShell CmdLets such as Get-Service
-When the server stalls I cannot...
- Log into to the server remotely or through Hyper-V. I can send the Ctrl-Alt-Del command to the VM, but it hangs before making it to the login screen.
- Connect to a network share hosted on the server
- Print anything. The spooler gets backed up and all printing stops.
I setup a performance alert and data collectors to track the % Processor Time for each process and the total % Processor Time. During the stall period, the total % Processor Time averaged about 5%. I also checked the memory on the host machine, and there was always at least a few GBs available.
There are other VM servers running simultaneously on the same host. All other VMs seem to be unaffected during the stall period.
The VM server eventually starts functioning normally after a stall period of anywhere from 10-30 min. I could not find any relevant errors or warnings in the event logs. Does anyone have any idea why the server stalls in this way? Is there anything else I can check to narrow down the problem?