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.1, Patch ESX410-201101203-UG: Updates ESX 4.1 vmware-esx-esxupdate (1027905)

Details

 

Product Versions ESX 4.1
Build For build information, see KB 1029353.
Patch Classification Critical
Severity Critical
Host Reboot Required No
Virtual Machine Migration or Shutdown Required No
PRs Fixed 537454
Affected Hardware N/A
Affected Software N/A
VIBs Included vmware-esx-esxupdate
Related CVE numbers N/A


 

Solution

Summaries and Symptoms

In the esxupdate utility, the dependency resolution does not match with the bulletin building policy. While installing ESX hosts, you will not see any errors or warning messages. After the installation, users can check the installed VIB information by running the esxupdate --vib-view query command in the service console. The bulletin delivery policy should be used to use the lowest version of VIB needed so that you can control the fixes you install and avoid unknown or unexpected updates to ESX hosts. This patch fixes the issue.

Deployment Considerations

None beyond the required patch bundles and reboot information listed in the table above.

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.1 hosts.

To update ESX 4.1 hosts without using Update Manager, download the patch ZIP file from http://support.vmware.com/selfsupport/download/ and install the bulletin by using esxupdate from the command line of the host. For more information, see the ESX 4.1 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

  • 0 Ratings

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)
  • 0 Ratings
Actions
KB: