ESX Server 3.5, Patch ESX350-200806405-BG: Update to VMware-esx-vmx

Summaries and Symptoms

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

• Virtual machines might hang during a VMotion move from ESX 3.5 to ESX 3.0.x hosts. (PR 255437)
  
  
• This change makes the socket file (named pipe) visible and available on a local, non-VMFS, ESX service console file system directory. (PR 225832)
  

Deployment Considerations

Requirements

Named Pipes

Named pipes must be created on a local, non-VMFS location on the service console file system directory. By default, this location is under /var/log/vmware/. Specify the full path for the Pipe Name entry. For example, use /var/log/vmware/pipes/server1, not pipes/server1.

Note: Power off a virtual machine before making changes to its serial port connection settings. Editing these settings while a virtual machine is running might cause the virtual machine to unexpectedly shut down.

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.