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-200906401-BG : Updates vmkctl and vmkernel RPMs (1011796)

Details

Release Date: June 30, 2009

Download Size:
22 MB
Download Filename:
ESX350-200906401-BG.zip
md5sum: 
803ecd0f076a5c61a71dda71b16ead45 


Product Versions ESX 3.5
Build 169697
Patch Classification Critical
Supersedes ESX350-200712409-BG
ESX350-200802412-BG
ESX350-200804401-BG
ESX350-200904409-BG
Requires ESX350-200810201-UG
ESX350-200903201-UG
ESX350-200904401-BG
ESX350-200904402-SG
ESX350-200905401-BG
Virtual Machine Migration or Reboot Required Yes
Host Reboot Required Yes
PRs Fixed 346862, 360308, and 395996
Affected Hardware N/A
Affected Software N/A
RPMs Included VMware-esx-vmkctl, VMware-esx-vmkernel
Related CVE numbers N/A

Solution

Summaries and Symptoms

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

  • When you power on virtual machines on ESX 3.5 hosts, many inactive VMFS volumes are opened in addition to the VMFS volume containing the virtual machine disk files. This might cause the virtual machines to take more time to boot. In a cluster environment, this issue might also cause VMotion operations to timeout on the destination host. This fix ensures that only the VMFS volumes on which the virtual machines reside are opened.
  • While performing a host rescan on ESXi, the host and virtual machines might stop responding till the end of the rescan operation. During this time, connections to virtual machines are lost, including SSH, client connections, and communication to other clustered storage modules. The virtual machines start responding after the rescan operation is completed.
  • Excessive cold migration of virtual machines between ESX hosts might cause ESX hosts to be disconnected from vCenter Server due to a memory leak on the host agent (hostd).

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. A reboot of the ESX Server host is required after applying this 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

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