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 ESXi, Patch ESXe350-200905401-I-BG: Firmware Update (1010964)

Details

Release Date: May 28, 2009

Download Size:
221 MB
Download Filename:
ESXe350-200905401-O-BG.zip
md5sum:
ae10a39ef6be09f55eb0bf80e86d3caf

Note: The three ESXi patches for Firmware "I", VMware Tools "T," and the VI Client "C" are contained in a single offline "O" download file.


Product Versions ESXi 3.5
Build 163429
Also see KB 1001179.
Patch Classification Critical
Host Reboot Required Yes
Virtual Machine Migration or Shutdown Required Yes
PRs Fixed 385373 324971 388035 279999 348747
Affected Hardware IBM, Fujitsu and SUN servers installed with Adaptec aacraid_esx30 driver, NFS data store
Affected Software N/A
Related CVE numbers N/A

Solution

Summaries and Symptoms

This patch fixes the following issues:

  • Virtual machines using a NFS data store might fail after a HA failover event. This issue might result in two scenarios:

    1. When you have memory overcommitment with virtual machines on a NFS datastore, it results in the creation of a vswp file, which is a non-zero size swap file. In this scenario if HA failover events occur and the HA has the setting "Leave VM powered on", then you might have a virtual machine failure on the host where the virtual machine was originally running before the HA event.

    2. If you do not have memory overcommitment with virtual machines on a NFS datastore, if HA failover events occur with the setting "Leave VM powered on", further vmotions of the virtual machine running on the original host might fail.

  • When an invalid license is specified to a license server or if the network is intermittent, the ESX server goes to an unlicensed state. The ESX server does not try again to acquire the licenses from the license server. This fix allows the ESX server to try to acquire licenses after a few minutes.
  • Addresses a robustness issue in VMX.
  • ESX 3.5 might fail on IBM, Fujitsu and SUN servers installed with Adpatec aacraid_esx30 driver. This issue occurs when ESX host is running management agents and heavy I/O load on the volumes owned by aacraid_esx30 driver.
  • This fix updates the tzdata package. The tzdata package contains data files with rules for various time zones around the world.

    This updated package addresses the following changes to Daylight Saving Time (DST) observations:

    * Future transition dates for Brazil were fixed
    * Several Argentinian provinces decided not to observe Daylight Saving

    Users in the affected locales, or users interacting with people or systems in the affected locales, are advised to upgrade to this updated package, which adds these enhancements.

Deployment Considerations

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

Patch Download and Installation

The typical way to apply patches to ESXi hosts is through the VMware Update Manager. For details, see the VMware Update Manager Administration Guide.

ESXi hosts can also be updated by downloading the most recent "O" (offline) patch bundle from http://support.vmware.com/selfsupport/download/ and installing the bundle using VMware Infrastructure Update or by using the vihostupdate command through the Remote Command Line Interface (RCLI). For details, see the ESX Server 3i Configuration Guide and the ESX Server 3i Embedded Setup Guide (Chapter 10, Maintaining ESX Server 3i and the VI Client) or the ESX Server 3i Installable Setup Guide (Chapter 11, Maintaining ESX Server 3i and the VI Client).

Note: ESXi hosts do not reboot automatically when you patch with the offline bundle.

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: