Knowledge Base

Summaries and Symptoms

This patch fixes the following issues or adds the following enhancements for ESX 3.5 Update 4:

• VMware ESX 3.5 Update 4 introduces an adaptive queue depth algorithm that adjusts the LUN queue depth in the VMkernel I/O stack. When congestion is detected, VMkernel throttles the LUN queue depth. VMkernel will attempt to gradually restore the queue depth when congestion conditions subside. By default, this algorithm is disabled. You can enable it by following the instructions in KB article 1008113 at http://kb.vmware.com/kb/1008113. Patch ESX350-200903216-UG is also required to complete this fix.
  
  
• Adds support for SUSE Linux Enterprise 11 guest operating systems.
  
  This patch adds support for SLES 11 guests. For more information about supported guests, see the Guest Operating System Installation Guide at http://www.vmware.com/pdf/GuestOS_guide.pdf.
  
  
• Updates VMware Tools from 3.1.1 to 3.1.2.
  
  
• Upgrading the Japanese version of VMware Tools from ESX 3.0.2 U1 to ESX 3.5 U1 on the guest operating system might fail resulting in an error message:
  
  An error occurred while the conversion. Check if the path is available.
  
  
• Adds support for passive mode FTP. Patch ESX350-200903202-UG is also required to complete this fix.
  
  
• Adds failover support for Sun StorageTek 2530. For more information about hardware compatibility, see http://www.vmware.com/resources/compatibility.
  
  
• Updates the Intel e1000e driver, which allows ESX 3.5 Update 4 to work with products based on the Intel 82574L Gigabit Ethernet controller. For detailed information about ESX hardware compatibility, see http://www.vmware.com/resources/compatibility. Patch ESX350-200903219-UG is also required to complete this fix.
  
  
• After applying patch ESX350-200811401-SG, all iSCSI LUNs become unavailable with software iSCSI. This issue is known to affect ESX systems with Adaptec Snapserver series and Dell NX series of NAS applicances. The problem is due to the way the software iSCSI driver propagates an overflow condition reported by the target.
  
  
• ESX 3.5 displays incorrect VMkernel warning messages.
  
  ESX 3.5 might display incorrect VMkernel warning messages, which indicate the system has detected a device that does not support SCSI-3 protocol. However, the device still works with ESX 3.5. The messages might look similar to the following:
  
  vmkwarning:Dec 12 14:57:11 [host name] vmkernel: 0:00:00:18.539 cpu5:1048)
  WARNING: ScsiUid: 550: Path 'vmhba2:C0:T0:L12' : supports ANSI version 'SCSI-2'
  (0x2). In order to be used with ESX a device must support the SCSI 3 protocol.
  
  This patch fixes the issue. The fix provides for logging a warning message similar to the following in the VMkernel logs, if a non-SCSI 3 device is detected:
  
  Support for SCSI-2 devices may be deprecated in a future release
  
  
• Guest operating systems and storage might not communicate properly in RDM.
  
  In Raw Device Mapping (RDM) mode, if the amount of data sent back from storage to the guest operating system is greater than 36 bytes in one SCSI inquiry, then guest operating systems and storage might not communicate properly. Products such as Microsoft Virtual Shadow Copy Service (VSS) and NetApp SnapDrive might experience issues. This patch resolves this issue.
  
  
• PAE-enabled Windows 2000 virtual machines stop responding.
  
  A Physical Address Extension (PAE) enabled Windows 2000 virtual machine might stop responding on reboot, or fail randomly.
  
  
• The maximum memory limits for Windows XP Professional, .NET Standard Server, and Vista have been raised to the following limits:
  
  XP - 65,532MB
  .NET - 32,768MB
  Vista - 4,096MB
  
  
• For specific guest operating systems, the BusLogic SCSI adapter is inaccurately listed as supported.
  
  When using the VI Client to view available adapters for the Windows Vista 32-bit or Windows Server 2008 32-bit guest operating systems, the BusLogic SCSI adapter is listed as supported. In fact, this adapter is not recommended.
  
  This issue is resolved in this release. Now, when you edit the SCSI controller settings of a virtual machine using Windows Vista 32-bit or Windows Server 2008 32-bit, BusLogic is listed as Not Recommended.
  
  
• The default virtual NIC has changed from vlance to e1000.
  
  For ESX Server 3.5 Update 4, the default vlance virtual NIC used for Solaris 10 32-bit and Solaris 9 32-bit has changed. To provide better performance, the E1000 network interface card (NIC) has been made the default virtual NIC for Solaris 9 32-bit and Solaris 10 32-bit.
  
  
• Enhanced vmxnet support has been added for the following guest operating systems:
  
  Microsoft Windows Server 2003, Standard Edition (32-bit)
  Microsoft Windows Server 2003, Standard Edition (64-bit)
  Microsoft Windows Server 2003, Web Edition
  Microsoft Windows Small Business Server 2003
  Microsoft Windows XP Professional (32-bit)
  Ubuntu (32-bit)
  
  The enhanced VMXNET adapter is now supported on ubuntu-32 and winxppro-32 guest operating systems on ESX 3.5 Update 4
  
  
• Present E1000 as an option for NetWare 5 and 6 guests, through the VI Client.
  
  Virtual machines running NetWare 5 and 6 can now be configured to use E1000 network adapters.
  
  
• Faster scans for ESX updates.
  
  VMware Update Manager 1.0 Update 2 and Update 3 take a longer time to scan ESX, compared to the time taken by Update Manager 1.0 and Update 1.
  
  Update Manager 1.0 Update 4 scans ESX for updates faster than Update 2 or Update 3.
  
  
• The default memory size for the Windows EBS 2008 64-bit guest is insufficient.
  
  Prior to ESX 3.5 Update 4, the guest operating system for Windows Essential Business Server (EBS) 2008 64-bit does not, by default, provide enough memory. At 2048MB, the default memory size is insufficient, resulting in the virtual machine failing to load.
  
  This issue is resolved in this patch. For ESX 3.5 Update 4, the default memory size for the Windows EBS 2008 64-bit guest operating system is 4096MB.
  
  
• Prior to ESX Server 3.5 Update 4, the installer stalls on systems using Intel Nehalem processors.
  
  
• The ESX 3.5 Update 3 Emulex driver is, in some cases, incompatible with the Emulex host bus adapter (HBA). When Emulex LPe1150 HBA with firmware version 1.00a5 or older is used with the Emulex driver shipped in ESX 3.5 Update 3, the driver fails to claim the Emulex HBA.
  
  This issue is resolved in this patch. The VMware driver for this issue has been updated in ESX 3.5 Server Update 4. The new driver is now also compatible with Emulex host bus adapters that use firmware versions 1.00a5 and older. The updated driver works irrespective of the Emulex HBA firmware version.
  
  This update also requires patch ESX350-200903211-UG for the complete fix.
  
  
• The driver and firmware for the QLogic HBAs have been updated to version 7.08-vm66 and 4.04.06 respectively. This upgrade provides support for the QLogic management application SANSurfer FC Manager.
  
  This update also requires patch ESX350-200903212-UG for the complete fix.
  
  
• The Emulex driver has been updated to version 7.4.0.39. This upgrade provides support for the Emulex management application HBAnyware.
  
  This update also requires patch ESX350-200903212-UG for the complete fix.
  
  
• This patch fixes the following known issue, which was introduced in ESX 3.5 Update 2: ESX Server VMkernel Does Not Recognize a Loaded IDE Controller and Displays an Error Message (KB 1004309).
  
  This update also requires patch ESX350-200903209-UG for the complete fix.
  
  
• The OpenIPMI driver has been enhanced to operate the HP IPMI controller through the PCI bus and interrupts, and to support OEM message channels. These changes are necessary for HP G6 servers, which use OEM messages, to report memory problems.
  
  
• This patch provides updated versions of LSI MPT SCSI and MegaRAID SAS drivers. The updated drivers allow Dell Open Manage management agents to run on ESXi without causing a spike in CPU utilization.
  
  Without this patch, the esxtop command shows output similar to the following for dsm_sa_datamgr3:
  
  ID GID NAME NWLD %USED %RUN %SYS %WAIT %RDY %IDLE %OVRLP %CSTP %MLMTD
  1973 1973 dsm_sa_datamgr3 14 67.88 68.88 0.00 1329.24 1.86 0.00 7.85 0.00 0.00
  
  This patch also requires bundle ESX350-200903201-UG for the VMnix kernel portion. This patch contains only the driver RPMs.
  
  Driver RPM versions:
  mptscsi_2xx - 2.6.48.18
  megaraid_sas driver - 3.19
  
  This update also requires patch ESX350-200903226-UG for the complete fix.
  
  
• This patch adds support for new HP Smart Array controllers. For details about supported I/O Devices, search the Hardware Compatibility Guide at http://www.vmware.com/resources/compatibility.
  
  This update also requires patch ESX350-200903210-UG for the complete fix.
  
  
• This patch adds support for the NetXen NX3031 network interface controller.
  
  Note: This NIC does not support network boot or network installation.
  
  This update also requires patch ESX350-200903218-UG for the complete fix.