Virtual machine CPU usage alarm
search cancel

Virtual machine CPU usage alarm

book

Article ID: 319458

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

This is one of a series of KB articles that provide information about default vSphere alarms for virtual machines. Default vSphere alarms are set on the vCenter Server level and propagated to all child objects in the inventory.
 
Alarm nameWarning ConditionCritical ConditionActions
Virtual machine CPU usageCPU usage is above 75% for 5 minutes.CPU usage is above 90% for 5 minutes.No default actions are set for this alarm.


Environment

VMware vCenter Server 5.5.x

Resolution

A short spike in CPU usage or CPU ready indicates that you are making the best use of the virtual machine resources. However, if the CPU usage value for a virtual machine is above 90% and the CPU ready value is above 20%, performance is being impacted.

If performance is impacted, consider taking the actions listed below.

  • Verify that VMware Tools is installed on every virtual machine on the host.
  • Set the CPU reservations for all high-priority virtual machines to guarantee that they receive the CPU cycles required.
  • Compare the CPU usage value of a virtual machine with the CPU usage of other virtual machines on the host or in the resource pool. In the Monitor tab of the vSphere Web Client, the stacked line chart on the host Virtual Machine view shows the CPU usage for virtual machines on the host.
  • Determine whether the high ready time for the virtual machine resulted from its CPU usage time reaching the CPU limit setting. If so, increase the CPU limit on the virtual machine.
  • Increase the CPU shares to give the virtual machine more opportunities to run. The total ready time on the host might remain at the same level if the host system is constrained by CPU. If the host ready time doesn't decrease, set the CPU reservations for high-priority virtual machines to guarantee that they receive the required CPU cycles.
  • Increase the amount of memory allocated to the virtual machine. This decreases disk and or network activity for applications that cache. This might lower disk I/O and reduce the need for the host to virtualize the hardware. Virtual machines with smaller resource allocations generally accumulate more CPU ready time.
  • Reduce the number of virtual CPUs on a virtual machine to only the number required to execute the workload. For example, a single-threaded application on a four-way virtual machine only benefits from a single vCPU. But the hypervisor's maintenance of the three idle vCPUs takes CPU cycles that could be used for other work.
  • If the host is not already in a DRS cluster, add it to one. If the host is in a DRS cluster, increase the number of hosts and migrate one or more virtual machines onto the new host.
  • Upgrade the physical CPUs or cores on the host if necessary.
  • Use the newest version of hypervisor software, and enable CPU-saving features such as TCP Segmentation Offload, large memory pages, and jumbo frames.

Additional Information

For translated versions of this article, see:

Additional Information

To View and edit Alarm setting Please refer to the link mention below: 
https://docs.vmware.com/en/VMware-vSphere/5.5/com.vmware.vsphere.monitoring.doc/GUID-B0E61111-CEE9-4141-A66B-00935AF3976D.html
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.monitoring.doc/GUID-B0E61111-CEE9-4141-A66B-00935AF3976D.html