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-200904401-I-SG: Firmware Update

Details

Release Date: April 29, 2009

Download Size:
221 MB
Download Filename:
ESXe350-200904401-O-SG.zip
md5sum:
9b11aa16afd676a5190cfd0b68d5a836

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 158874
Also see KB 1001179.
Patch Classification Security
Host Reboot Required Yes
Virtual Machine Migration or Shutdown Required Yes
PRs Fixed

313588 322534 351147 352697 355266 357182 360978 361659 363479 378678 346708 344303 336846 346732 336284 252894 353326 367862

Affected Hardware QLogic FC HBAs
Affected Software

Solaris 10 guest operating systems

Related CVE numbers N/A

Solution

Summaries and Symptoms

This patch fixes the following issues:

  • Fixes an issue where ESX might fail if a SCSI read command is split for a tape device. Splitting commands is not supported for tape devices. After this fix is applied split SCSI commands will fail but this will not cause ESX to fail.
  • Fixes an issue where VirtualCenter fails to collect performance data from hosts if the initial interval for which the data is requested is longer than one hour.
  • Fixes an issue in the VMkernel TCP/IP stack where adding a system to an HA (High Availability) cluster results in a timeout error.
  • Fixes an issue where a virtual machine might fail if a reserved register is accessed within the guest operating system.
  • Fixes an issue where the VMware Tools configuration script might fail on a Solaris 10 guest operating system if an X server is not installed.
  • Fixes an issue where a virtual machine might stop responding or the progress bar in the graphical user interface might appear to be stuck at 95% when you consolidate a snapshot of a powered on virtual machine.
  • Fixes an issue where ESX Server might stop responding because of a memory leak that occurs when an open call to a character device driver fails.
  • Fixes an issue where ESX might fail when a guest operating system uses the Vmxnet2 virtual network adapter.
  • Fixes an issue where a virtual machine might stop responding in certain situations due to fragmented guest operating system memory and a heavy load on the LUN that holds the deltadisk. In this case, error messages similar to the following might appear in the vmkernel log:
    Cow: <#>: IO to deltadisk handle <#> failed: Busy
  • Fixes an issue where hostd might fail, which causes VirtualCenter to report the ESX host as disconnected.
  • Fixes an issue where ESX might fail due to the race between the normal completion of a fragmented I/O command and completion as a result of the cancellation of the same command.
  • Fixes an issue where a virtual machine might fail if there is an empty string in the virtual machine configuration.
  • Fixes an issue where an unsuccessful online consolidation might cause a virtual machine to fail and become unusable because of a CID mismatch.
  • Fixes an issue where the nfsclient heap runs out of memory when 32 volumes are mounted. If the nfsclient heap runs out of memory, error messages might display virtual machines as disconnected, inaccessible or invalid. The maximum heap size is increased from 6MB to 12MB.
  • Fixes an issue where two rescans are required to discover a new LUN connected to a Qlogic Fibre Channel HBA. This is due to a rescan timing issue between VMkernel and Qlogic Fibre Channel driver.
  • Fixes an issue where ESX might fail due to a deadlock condition in the bnx2 driver.
  • Fixes an issue where the ESX software iSCSI initiator fails to recognize newly created storage devices.
  • On ESXi 3.5, the system might fail to reboot. This occurs when the following Sysalert warning is observed in vmkernel logs:
    ALERT: UserCartel: 993: bootstrap/init UW died

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


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