There is a very interesting thing with virtualization hosts like Hyper-V or ESX that get CPU spikes from SCOM script. Basically this happens every x Minutes, the interval that the rule/monitor is configured to run a specific script. The latest observed script is SCOMpercentageCPUTimeCounter.vbs which is part of the MicrosoftSystemCenter2007 management pack. Apparently this one runs by default every 5 minutes, causing high CPU spikes on the host and a temporary 3-5 seconds freeze on the guest OS. very unpleasant for the users..
The workaround for this is to configure the synctime for the datasource module type Microsoft.SystemCenter.HealthService.SCOMpercentageCPUTimeCounterDataSource -> http://blogs.technet.com/b/kevinholman/archive/2014/01/08/using-the-sync-time-property-in-workflows-and-overrides.aspx
or configure an override to use SpreadInitializationOverInterval -> http://operatingquadrant.com/2009/10/12/scom-distributing-workflows-with-the-spreadinitializationoverinterval-scheduler-parameter/
I`ve opened a connect suggestion for directly implementing SpreadInitializationOverInterval for the datasource. You can vote up for it from here: https://connect.microsoft.com/WindowsServer/feedback/details/888559/implement-also-spreadinitializationoverinterval-in-the-scompercentagecputimecounter-datasource