Re: how to diagnose a failure: hypervisor ran fine for months, then VMs slowed to a crawl, then hypervisor became non-responsive

It looks like I didn't actually apply Update 3 even though I was set to do it, probably because of issues regarding scheduling downtime.

I will do that as soon as I can schedule the downtime.

Thanks.