I recently bought a new system, which works just fine. I installed Windows 2012 R2, installed a SSD drive and 3 Western Digital 4Tb Red drives. I've created my Storage pools and installed the hyper-v role. I've also patched Windows through the normal Windows update process. I started building the 1st VM machine on this system.
What I'm noticing is that the VM will tend to go into a critical state. If I stop it the machine will go into a stopping-critical state. If I leave the machine running it can sometimes go into a running-critical state. Restarting the host machine doesn't solve the problem. Restarting the Hyper-v server doesn't seem to resolve the issue either. And more importantly, it seems that the Hyper-v management interface refreshes VMs slowly. Note, the rest of Windows operates great. The switches and buttons inside Hyper-v respond fine, but the VMs don't work hardly at all. I've tried using generation 1 and generation 2 VMs, it doesn't tend to make much of a difference.
I thought at first that maybe my drives were just slow so I created a new VM on my SSD, which does something like 90,000 IOPS and tried it there. I get the same behavior. I think this issue looks like a coding problem with Hyper-v more so than an environment problem with Windows or the hardware.
Is this a known issue by Hyper-v? Why do VMs go into a critical state so often?What's the deal?
What logs are best to look at in this situation?