Archives

tickermcse76

SCVMM Hypervisor host rebooting/crashing due to excessive CPU utilization

First off, I come from a VMWare ESXi background and have little exposure to HyperV.

There is a small 2 node cluster I inherited on SCVMM 2012 R2.  On occasion one of the hypervisor nodes will flatline at 100% CPU utilization which eventually causes it to crash.  All the VM’s will then migrate to node that’s left standing. 
With the new load in addition to th existing load the second node will then proceed to flatline at 100% CPU and crash.  On the next cycle, the VMs will all live on one hypervisor, and the ones with resources will be online, the ones without resources
will be in a failed state.

In VMWare, if you over provisioned CPU’s the VM performance would get sluggish but there would never be the case where VM usage would directly crash ESXi.  I realize HyperV is a different model in the sense that the Hypervisor is still running on top
of Windows OS; but is there some control I can put into place that prevents above scenario?

Read full post . . . .

What is the quickest way to review a VM’s recent migration history?

I’m very familiar with VMWare ESXi - but new to Hyper-V.  In VMWare you can query the central cluster vCenter logs to determine the vmotion migration history of a VM no matter which host it moves to/from.

What is the most efficient way to do this in Hyper-V?  What I have found so far is I need to login to each Hyper-V host and query the log Microsoft-Windows-Hyper-V-VMMS-Admin.  I suppose I could query all the logs remotely - but is there a better
way to do this?

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 40 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3363