I've searched the VMTN forums haven't found anything relevant yet. Thanks much for your ideas and recommendations!
After using Converter to P2V several of our older Windows 2003 servers, a few of the VMs started showing the following alert in MOM:
Alert Source: Processor: % Interrupt Time: _Total
Alert Description: Extremely high processor activity detected. Processor: % Interrupt Time: _Total value = 11.3750464279179. The average over last 6 samples is 11.375.
Alert Severity: Critical Error
I understand this alert indicates the following:
% Interrupt Time is the time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. suspends normal thread execution during interrupts. This counter displays the average busy time as a percentage of the sample time.
So...does anyone know why this alert would only show on a select few VMs? Should I adjust the monitoring threshold in MOM and forget about it? Or does something in the OS or hardware need tweaking?
Thanks so much - this community rocks!
Sounds like it could be indicative of an overloaded host with high %RDY times....
Also, possibly a wrong HAL?
--Matt
Thanks much for the reply. Both servers running 2 CPU, both running ACPI Multi-Proc HAL.
Host is very lightly used, CPU Ready% of <1% for this VM. In VC, this VM is showing CPU Ready average of 94 Milliseconds.
Any luck on this problem? I'm having the same notice on several of my VMs. All W2K3.
I have the same issue as well with a dual proc W2K3 server. The cluster it is in is not heavily used and processor ready times for this server are in line with other servers on the cluster that do not get this error.
Hello..
Did anyone find solution for this issue yet??
Its not impacting the applications running on the server, but my SCOM is creating lot of noise for this alert for 2 servers.