tomsimmons

Chris When you say that it prevents additional memory being assigned under dynamic, does that include after the service has been restarted on machines that were still running? Some of our guests don't get touched for a period of time, so Hyper-V will had cut their resources right the way back. If that machine is isn't stuck in the stopping state, but vmcompute is restarted to resolve others that are, I'm wondering if that machine won't be assigned more resource (RAM) when it does gets used unless it has also been restarted after the vmcompute restarts. Where did you find the crash log you posted? Tom

Chris You haven't seen anything to suggest it is related to Windows updates of the guests? It is upon the restart of guests post updates that ours seems most likely to fail. When you say you stopped using dynamic memory, that is per machine you have set a fixed and permanently assign RAM size? Tom

Chris When you terminate vmcompute the second time, do you have to resort to a brutal process kill again, or does the service stop cleanly from the services manager? Tom

Steve We have NUMA turned off, not sure if we should or not, wasn't my decision don't know the reasoning behind the decision. I do recall someone mentioning this before, and seeing a KB, but can I find it now. We have 2 identical servers in a singe rack case, they don't work as a cluster, they are fully independent. I don't have the CPU & RAM specs to hand, but I do know that all the memory is identical performance in each server, so not sure NUMA would offer much to us. Do you have the KB number to hand, or can you recall the jist of what was being said? Tom

We are having the same problem using Hyper-V 2016 Server (the non GUI set up). It does seem to tie into Terens' theory that it is update related, it always seems to happen after updates have been applied to the guest, nothing to do with the host. Has anyone found a solution to this yet? I tried the restarting the vmcompute service, it fails to stop, but terminating it through task manager then restarting I can the see all the stuck machines shown with a status of Off. However you can't restart them, they all response with a catastrophic failure message. restarting the host clears this. Tom