Saturday, 3 August 2013

Host CPU Spikes at 100 Percent when install new VM

You experience high CPU usage in the guest operating system. However, when you examine Task Manager, no CPU usage issues are displayed in the host operating system.
There are instances where performance problems or symptoms may arise, but the cause may be due to the VM environment/configuration. The information and screenshots provided below are available to help determine if the performance problem may exist due to virtual instance instead of at the Traveler level.
Please check the following areas to determine if the VM is the cause of the performance related issue.
Check for VM Alarms
Click the Alarms tab to determine if there are any alerts available.

This example shows a high CPU Alarm condition for the timeframe being investigated. Engage your VMWare team as soon as possible to investigate errors such as these.

Check the CPU of the Traveler server by following these steps:
Click the Performance tab.
Click the "Advanced" button

Click the "Chart Options..." link
For CPU, choose "Past week" or the appropriate time frame for investigation.
Under the Counters section, check the boxes for "Usage" and "Ready"

Click Apply / OK
Save the chart (screenshot or click the save icon in the top right)
Notice that one of these (the Usage one) is in percentage of CPU. The key is to look for critical thresholds and peak times. Look for patterns.

Usage = CPU Usage as a percentage during the interval (during the amount of time that was selected)
Ready = Percentage of time that the virtual machine was ready, but could not get scheduled to run on the physical CPU.
A short spike in CPU usage or CPU ready indicates that the system is making the best use of the host resources. However, if both values are constantly high, the hosts are probably overcommitted. Generally, if the CPU usage value for a virtual machine is above 90% and the CPU ready value is above 20%, performance is impacted.
It can be many reason for 100 CPU spike by the host, one of the hardware compatibility issue can be also for 100 CPU spike.
Poor performance when virtual machines reside on local storage on VMware ESXi 5.0 Affected configurations
The system may be any of the following IBM servers:
  • BladeCenter HS23, type 7875, any model
The system is configured with at least one of the following:
  • UpdateXpress Service Pack Installer, any version
  • VMware vSphere Hypervisor 5.0 with IBM Customization Installable, Base Install
This tip is not option specific.
The mpt2sas device driver for the VMware ESXi 5.0 is affected.
  • VMware ESXi 5.0
  • Solution
  • Issue the following esxcli commands in the ESXi Shell to remove ilfu and LSIProvider VIBs.
 esxcli software vib remove -n ilfu
esxcli software vib remove -n LSIProvider

No comments:

Post a Comment