Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

VMware ESX 4.0, Patch ESX400-200906404-BG: Updates CIM

Details

Release Date: July 9, 2009

Download Size:
396.3 MB
Download Filename:
ESX400-200906001.zip
md5sum:
cab549922f3429b236633c0e81351cde
sha1sum:
aff76554ec5ee3c915eb4eac02e62c131163059a
Product Versions ESX 4.0
Build 175625
Also see KB 1012514.
Patch Classification Critical
Host Reboot Required No
Virtual Machine Migration or Shutdown Required No
PRs Fixed 396800
Affected Hardware N/A
Affected Software Openwsman
VIBs Included vmware-esx-cim
vmware-hostd-esx
Related CVE numbers N/A

Solution

Summaries and Symptoms

Issues fixed in this patch (and their relevant symptoms, if applicable) include:

  • Fixes a memory leak issue with Openwsman in ESX/ESXi.

Deployment Considerations

If you are using CIM providers such as the EMC PowerPath CIM Module and you apply this patch, you will receive an error message that indicates that the CIM provider is unreachable. For example, when using EMC PowerPath, the errror message reads:
PowerPath CIM provider unreachable
To resolve the issue, log in to the service console for each affected ESX host and run the /usr/sbin/cim-install.sh script.

Patch Download and Installation

See the VMware vCenter Update Manager Administration Guide for instructions on using Update Manager to download and install patches to automatically update ESX 4.0 hosts.

To update ESX 4.0 hosts when not using Update Manager, download the patch zip file from http://support.vmware.com/selfsupport/download/ and install the bulletin using esxupdate from the command line of the host. For more information, see the ESX 4 Patch Management Guide.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
Actions
KB: