Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

CPU Utilization Peaks After Installing Dell OpenManage (1004508)

Last Updated: 4/13/2011Categories: TroubleshootingTotal Views: 9685Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

On my ESX Server with Dell OpenManage installed, I notice regular spikes of very high CPU utilization.

Solution

The magnitude of the spike in CPU utilization is a metering artifact of the IPMI interface.

The IPMI system management driver may consume a lot of CPU, but it does this with low priority, so it should not block other CPU users. It uses much less CPU on a busy system. It basically soaks up what would otherwise be idle time.

During the high peak periods, the kipmi0 thread is attributed because it's always expecting data, and it's always ready to run. It can only read one char at a time, so when it's done it calls schedule() so any other process that's ready to run can go. Sleeping for a clock tick is way too long to wait, so it loops on polling the status register and calling schedule(). In this way, either another process is using the CPU or kipmi0 is, at all times. This persists until IPMI is no longer waiting for a response, at which time it goes into a more patient poll()ing cycle. Since none of the other processes are grabbing a lot of CPU time, kipmi0 is typically assigned the usage.

A possible workaround is to configure the IPMI driver to poll only on the clock tick. This causes the apparent CPU usage to essentially disappear, at the expense of dropping the performance of IPMI data acquisition by several times. To slow the IPMI sensor queries, pass the parameter si_force_kipmid=1 when loading the ipmi_si_drv module.

To do this:

Edit the file /etc/init.d/ipmi

Change the line:

modprobe $IPMI_SI_MODULE_NAME > /dev/null 2>&1

To:

modprobe $IPMI_SI_MODULE_NAME si_force_kipmid=1 > /dev/null 2>&1 # disable kipmi0

The change takes effect on the next system reboot.

Additional Information

For translated versions of this article, see:

日本語：Dell OpenManage のインストール後に CPU 使用率がピークになる （1035764）

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Mobile Appliance での VMware Tools のインストールとアップグレード (2001191)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
vSphere Management Assistant 内部に .ISO イメージをマウントする (1024143)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESX Server

Related Versions:

VMware ESX Server 3.5.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant