Knowledge Base

Summaries and Symptoms

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

• 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.
  

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.

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.