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 3.5, Patch ESX350-200906408-BG: Updates VMX RPM (1011802)

Details

Release Date: June 30, 2009

Download Size:
7.3 MB
Download Filename:
ESX350-200906408-BG.zip
md5sum:
6d468ce85fa1c1d2aad2c9e24b1ce2d3


Product Versions ESX 3.5
Build 169697
Patch Classification Critical
Supersedes ESX350-200802411-BG
ESX350-200804402-BG
ESX350-200806405-BG
ESX350-200904201-SG
ESX350-200905402-BG
Requires ESX350-200810201-UG
ESX350-200903201-UG
ESX350-200904401-BG
ESX350-200904402-SG
Virtual Machine Migration or Reboot Required Yes
Host Reboot Required No
PRs Fixed 361287
Affected Hardware N/A
Affected Software N/A
RPMs Included VMware-esx-vmx
Related CVE numbers N/A

Solution

Summaries and Symptoms

This patch fixes an issue where virtual machines that use the Virtual Machine Interface (VMI) might stop responding.

Deployment Considerations

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

Patch Download and Installation

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

Note: All virtual machines on the host must be either shut down or migrated using VMotion before applying the patch.

To update ESX Server 3.5 hosts when not using Update Manager, download the most recent patch bundle from http://www.vmware.com/download/vi/vi3_patches_35.html and install the bundle using esxupdate from the command line of the host. For more information, see the ESX Server 3 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: