Release date: March 11, 2014

For more information on patch and update classification, see KB 2014447 . To search for available patches, see the Patch Manager Download Portal.

Summaries and Symptoms

This patch updates the esx-base, tools-light, rste, net-e1000e, scsi-mpt2sas, lsi-msgpt3, mtip32xx-native, sata-ahci, scsi-megaraid-sas, net-igb, net-tg3 VIBs to resolve the following issues:

• PR 1035387: When you attempt to retrieve the value for the resourceCpuAllocMax and resourceMemAllocMax system counters against the host system, the ESX host returns incorrect values. This issue is observed on a vSphere client connected to a vCenter Server.
  
  
• PR 1054246: When you run exscli hardware ipmi sdr list command, you might see an error similar to the following for used up resources:
  No records or incompatible version or read failed
  
  
• PR 1054760: Fibre Channel Host Bus Adapter (HBA) speed is displayed incorrectly as zero for some ESXi hosts on Managed Object Browser (MOB).
  
  
• PR 1055755: When VMX passes a VPN value to read a page, VMKernel fails to find a valid machine page number for that VPN value which results in the host failing with a purple diagnostic screen.
  
  
• PR 1072202: You might be unable to configure High Availability (HA). Error messages similar to the following might be written to the vpxd log file:
  
  vpxd-1967.log:2013-04-06T01:35:02.156+09:00 [07220 warning 'DAS'] [FdmManager::ReportMasterChange] VC couldn't find a master for cluster HA_GD for 120 seconds
  vpxd-1968.log:2013-04-06T05:02:55.991+09:00 [07320 warning 'DAS'] [FdmManager::ReportMasterChange] VC couldn't find a master for cluster HA_ID for 120 seconds
  
  This issue occurs when the hostd function runs out of sessions and error messages similar to the following are written to hostd log file:
  
  SOAP session count limit reached.
  
  
• PR 1073615: ESXi host experiences a purple diagnostic screen with errors for E1000PollRxRing and E1000DevRx when the rxRing buffer fills up and the max Rx ring is set to more than 2. The next Rx packet received that is handled by the second ring is NULL, causing a processing error. The purple diagnostic screen displays entries similar to the following:
  
  @BlueScreen: #PF Exception 14 in world 63406:vmast.63405 IP 0x41801cd9c266 addr 0x0
  PTEs:0x8442d5027;0x383f35027;0x0;
  Code start: 0x41801cc00000 VMK uptime: 1:08:27:56.829
  0x41229eb9b590:[0x41801cd9c266]E1000PollRxRing@vmkernel#nover+0xdb9 stack: 0x410015264580
  0x41229eb9b600:[0x41801cd9fc73]E1000DevRx@vmkernel#nover+0x18a stack: 0x41229eb9b630
  0x41229eb9b6a0:[0x41801cd3ced0]IOChain_Resume@vmkernel#nover+0x247 stack: 0x41229eb9b6e0
  0x41229eb9b6f0:[0x41801cd2c0e4]PortOutput@vmkernel#nover+0xe3 stack: 0x410012375940
  0x41229eb9b750:[0x41801d1e476f]EtherswitchForwardLeafPortsQuick@<None>#<None>+0xd6 stack: 0x31200f9
  0x41229eb9b950:[0x41801d1e5fd8]EtherswitchPortDispatch@<None>#<None>+0x13bb stack: 0x412200000015
  0x41229eb9b9c0:[0x41801cd2b2c7]Port_InputResume@vmkernel#nover+0x146 stack: 0x412445c34cc0
  0x41229eb9ba10:[0x41801cd2ca42]Port_Input_Committed@vmkernel#nover+0x29 stack: 0x41001203aa01
  0x41229eb9ba70:[0x41801cd99a05]E1000DevAsyncTx@vmkernel#nover+0x190 stack: 0x41229eb9bab0
  0x41229eb9bae0:[0x41801cd51813]NetWorldletPerVMCB@vmkernel#nover+0xae stack: 0x2
  0x41229eb9bc60:[0x41801cd0b21b]WorldletProcessQueue@vmkernel#nover+0x486 stack: 0x41229eb9bd10
  0x41229eb9bca0:[0x41801cd0b895]WorldletBHHandler@vmkernel#nover+0x60 stack: 0x10041229eb9bd20
  0x41229eb9bd20:[0x41801cc2083a]BH_Check@vmkernel#nover+0x185 stack: 0x41229eb9be20
  0x41229eb9be20:[0x41801cdbc9bc]CpuSchedIdleLoopInt@vmkernel#nover+0x13b stack: 0x29eb9bfa0
  0x41229eb9bf10:[0x41801cdc4c1f]CpuSchedDispatch@vmkernel#nover+0xabe stack: 0x0
  0x41229eb9bf80:[0x41801cdc5f4f]CpuSchedWait@vmkernel#nover+0x242 stack: 0x412200000000
  0x41229eb9bfa0:[0x41801cdc659e]CpuSched_Wait@vmkernel#nover+0x1d stack: 0x41229eb9bff0
  0x41229eb9bff0:[0x41801ccb1a3a]VmAssistantProcessTask@vmkernel#nover+0x445 stack: 0x0
  0x41229eb9bff8:[0x0]<unknown> stack: 0x0
  
  
• PR 1073966: Whenever you reset a management network where the management traffic is enabled on multiple VMkernel ports, the IP address displayed on the Direct Console User Interface (DCUI) changes.
  
  
• PR 1074911: ESXi hosts with DvFilter module might display a purple diagnostic screen with a backtrace similar to the following:
  
  2013-07-18T06:41:39.699Z cpu12:10669)0x412266b5bbe8:[0x41800d50b532][email protected]#v2_1_0_0+0x92d stack: 0x10
  2013-07-18T06:41:39.700Z cpu12:10669)0x412266b5bc68:[0x41800d505521][email protected]#v2_1_0_0+0x394 stack: 0x100
  2013-07-18T06:41:39.700Z cpu12:10669)0x412266b5bce8:[0x41800cc2083a]BH_Check@vmkernel#nover+0x185 stack: 0x412266b5bde8, 0x412266b5bd88,
  
  
• PR 1075046: In an ESXi host, when reading the Field Replaceable Unit (FRU) inventory data using the Intelligent Platform Management Interface (IPMI) tool, the vmklinux_9:ipmi_thread of vmkapimod displays the CPU usage as hundred percent. This is because the IPMI tool uses the Read FRU Data command multiple times to read large inventory data.
  
  
• PR 1076102: ESXi hosts might fail with a purple screen and display error messages similar to the following:
  
  2013-02-22T15:33:14.296Z cpu8:4104)@BlueScreen: #PF Exception 14 in world 4104:idle8 IP 0x4180083e796b addr 0x1
  2013-02-22T15:33:14.296Z cpu8:4104)Code start: 0x418007c00000 VMK uptime: 58:11:48:48.394
  2013-02-22T15:33:14.298Z cpu8:4104)0x412200207778:[0x4180083e796b]ether_output@<None>#<None>+0x4e stack: 0x41000d44f360
  2013-02-22T15:33:14.299Z cpu8:4104)0x4122002078b8:[0x4180083f759d]arpintr@<None>#<None>+0xa9c stack: 0x4100241a4e00

  This issue occurs due to race conditions in ESXi TCP/IP stack.

• PR 1078867: When the lsilogic virtual adapter executes an scsi target reset command, it waits for I/O completion on all the targets available in the virtual adapter. This might cause virtual machines with multiple virtual disks configured in lsilogic virtual adapter to become unresponsive.
  
  
• PR 1080038: When large number of parallel HTTP GET /folder URL requests are sent to hostd, the hostd service fails. This stops from adding the host back to the VCenter Server. An error message similar to the following might be displayed:
  
  Unable to access the specified host, either it doesn't exist, the server software is not responding, or there is a network problem.
  
  
• PR 1080309: Virtual machines with hardware version earlier than version 10 cannot connect to Open Virtual Switch (OVS) network.
  
  
• PR 1085140: vSphere Web Client might fail to recognize that VMware Tools is installed for Linux guest operating systems. Error message similar to the following might be displayed under Summary tab in vSphere Web Client:
  
  VMware Tools is not installed on this virtual machine.
  
  
• PR 1085511: The VMX process might fail when you attempt to power off a virtual machine. Error message similar to the following might be written to vmware.log file:
  
  Unexpected signal: 11
  
  
• PR 1091043: On an ESXi host when bandwidthCap and throughputCap are set at the same time, the I/O throttling option might not work on virtual machines. This happens because of incorrect logical comparison while setting the throttle option in SCSI scheduler.
  
  
• PR 1092686: On machines with Hyper Threading enabled, the vSphere Client core utilization value of the CPU is doubled compared to the value found while using esxtop core utilization.
  
  
• PR 1095225: When the Network Healthcheck feature is enabled and it handles many Healthcheck packets, the L2Echo function might not be able to handle high network traffic and the ESXi hosts might fail with a purple diagnostic screen similar to the following:
  
  2013-06-27T10:19:16.074Z cpu4:8196)@BlueScreen: PCPU 1: no heartbeat (2/2 IPIs received)
  2013-06-27T10:19:16.074Z cpu4:8196)Code start: 0x418024600000 VMK uptime: 44:20:54:02.516
  2013-06-27T10:19:16.075Z cpu4:8196)Saved backtrace from: pcpu 1 Heartbeat NMI
  2013-06-27T10:19:16.076Z cpu4:8196)0x41220781b480:[0x41802468ded2]SP_WaitLockIRQ@vmkernel#nover+0x199 stack: 0x3b
  2013-06-27T10:19:16.077Z cpu4:8196)0x41220781b4a0:[0x4180247f0253]Sched_TreeLockMemAdmit@vmkernel#nover+0x5e stack: 0x20
  2013-06-27T10:19:16.079Z cpu4:8196)0x41220781b4c0:[0x4180247d0100]MemSched_ConsumeManagedKernelMemory@vmkernel#nover+0x1b stack: 0x0
  2013-06-27T10:19:16.080Z cpu4:8196)0x41220781b500:[0x418024806ac5]SchedKmem_Alloc@vmkernel#nover+0x40 stack: 0x41220781b690...
  2013-06-27T10:19:16.102Z cpu4:8196)0x41220781bbb0:[0x4180247a0b13]vmk_PortOutput@vmkernel#nover+0x4a stack: 0x100
  2013-06-27T10:19:16.104Z cpu4:8196)0x41220781bc20:[0x418024c65fb2][email protected]#1.0.0.0+0x85 stack: 0x4100000
  2013-06-27T10:19:16.105Z cpu4:8196)0x41220781bcf0:[0x418024c6648e][email protected]#1.0.0.0+0x4b1 stack: 0x0
  2013-06-27T10:19:16.107Z cpu4:8196)0x41220781bfa0:[0x418024c685d9][email protected]#1.0.0.0+0x7f8 stack: 0x4122
  2013-06-27T10:19:16.108Z cpu4:8196)0x41220781bff0:[0x4180246b6c8f]vmkWorldFunc@vmkernel#nover+0x52 stack: 0x0
  
  
• PR 1109576: When the monitored hardware status is changed on an ESXi host on which SNMP is enabled and third-party CIM providers installed, you might not receive SNMP traps. Messages similar to the following are logged in the syslog file:
  
  2013-07-11T05:24:39Z snmpd: to_sr_type: unable to convert varbind type '71'
  2013-07-11T05:24:39Z snmpd: convert_value: unknown SR type value
  02013-07-11T05:24:39Z snmpd: parse_varbind: invalid varbind with type 0 and value: '2'
  2013-07-11T05:24:39Z snmpd: forward_notifications: parse file '/var/spool/snmp/1373520279_6_1_3582.trp' failed, ignored
  
  
• PR 1109856: The performance statistics calculation for virtual disk throughput is measured incorrectly in Bytes per second unit.
  
  
• PR 1111389: During vMotion of a virtual machine that has a vNIC connected to VDS, port files from the vMotion source host are not cleared from .dvsData directory even after a while.
  
  
• PR 1113575: Virtual machine might fail to boot if you disable Legacy Floppy Disk in the BIOS. This issue occurs when you follow the steps below:
  1. Create a virtual machine without an operating system.
  2. Use the Virtual Machine Settings to configure the CD or DVD to connect to an ISO image file or a physical drive to install the guest operating system.
  3. Disable Legacy Floppy Disk in the BIOS.
  
  After you disable Legacy Floppy Disk in the BIOS, the virtual machine beeps twice and fails to boot.
  
  
• PR 1114382: The unit received on entering the command esxcli network nic coalesce get output is milliseconds. The correct unit is microseconds.
  
  
• PR 1114973: You might find the Virtual Machine File System datastore missing from the Datastore tab of vCenter Server or an event similar to the following is displayed in the Events tab:
  
  XXX esx.problem.vmfs.lock.corruptondisk.v2 XXX or At least one corrupt on-disk lock was detected on volume [[Image:prio1.png]] ({2}). Other regions of the volume might be damaged too.

  The following message is logged in the vmkernel.log file:

  [lockAddr 36149248] Invalid state: Owner 00000000-00000000-0000-000000000000 mode 0 numHolders 0 gblNumHolders 4294967295ESC[7m2013-05-12T19:49:11.617Z cpu16:372715)WARNING: DLX: 908: Volume 4e15b3f1-d166c8f8-9bbd-14feb5c781cf ("XXXXXXXXX") might be damaged on the disk. Corrupt lock detected at offset 2279800: [type 10c00001 offset 36149248 v 6231, hb offset 372ESC[0$

  You might also see the following message logged in the vmkernel.log file:

  2013-07-24T05:00:43.171Z cpu13:11547)WARNING: Vol3: ValidateFS:2267: XXXXXX/51c27b20-4974c2d8-edad-b8ac6f8710c7: Non-zero generation of VMFS3 volume: 1

• PR 1116199: After installing EMC PowerPath, local datastores are not claimed by any Multi Path Plugin (MPP). When the claim rules are run, if a path matches a claim rule, that path is offered to the MPP. In vSphere 5.1, if the MPP returns a failure, then that path will be matched with other claim rules, and incase of a match, the path is offered to the MPP in those claim rules. If a path is not claimed by any MPP, it is offered to NMP due to the catch-all claim rule.
  
  
• PR 1124192: In vCenter performance chart, the net.throughput.usage related value is in kilobytes, but the same value is returned in bytes in theVMkernel. This leads to incorrect representation of values in the vCenter performance chart.
  
  
• PR 1124983: During a VMkernel System Information (VSI) call from the userworld program ps, the VMkernel experiences an error when the instance list sent to the kernel is corrupted. The issue occurs if the numParams is too high and the kernel tries to access the array of that index. A purple diagnostic screen with a backtrace is displayed similar to the following:

  2013-09-06T00:35:49.995Z cpu11:148536)@BlueScreen: #PF Exception 14 in world 148536:ps IP 0x418004b31a34 addr 0x410019463308

  PTEs:0x4064ffe023;0x2080001023;0x100065023;0x0;

  2013-09-06T00:35:49.996Z cpu11:148536)Code start: 0x418004800000 VMK uptime: 2:11:35:53.448
  2013-09-06T00:35:49.996Z cpu11:148536)0x412250e1bd80:[0x418004b31a34]VSIVerifyInstanceArgs@vmkernel#nover+0xf3 stack: 0x410009979570
  2013-09-06T00:35:49.997Z cpu11:148536)0x412250e1bdd0:[0x418004b31bbb]VSI_CheckValidLeaf@vmkernel#nover+0xca stack: 0x8c8
  2013-09-06T00:35:49.998Z cpu11:148536)0x412250e1be40:[0x418004b32222]VSI_GetInfo@vmkernel#nover+0xb1 stack: 0x4100194612c0
  2013-09-06T00:35:49.999Z cpu11:148536)0x412250e1beb0:[0x418004ca7f31]UWVMKSyscallUnpackVSI_Get@<None>#<None>+0x244 stack: 0x412250e27000
  2013-09-06T00:35:50.000Z cpu11:148536)0x412250e1bef0:[0x418004c79348]User_UWVMKSyscallHandler@<None>#<None>+0xa3 stack: 0x0
  2013-09-06T00:35:50.001Z cpu11:148536)0x412250e1bf10:[0x4180048a8672]User_UWVMKSyscallHandler@vmkernel#nover+0x19 stack: 0xffea48d8
  2013-09-06T00:35:50.001Z cpu11:148536)0x412250e1bf20:[0x418004910064]gate_entry@vmkernel#nover+0x63 stack: 0x0
  2013-09-06T00:35:50.004Z cpu11:148536)base fs=0x0 gs=0x418042c00000 Kgs=0x0

• PR 1127952: The ESXi 5.5 host might generate hostd-worker dump after you detach a software iSCSI disk, that is connected with vmknic on vDS. This issue occurs when you attempt to retrieve the latest information on the host.
  
  
• PR 1127955: When you add shared nonpersistent read only disks to a virtual machine, the virtual machine might take longer time for the disk removal task operation.
  
  
• PR 1131013: While attempting to reset the CPUID mask on a virtual machine, hostd crashes when the value of SetRegisterInfo is NULL or an empty string.
  
  
• PR 1131638: When you provision and customize a virtual machine from a template on a vDS with Ephemeral Ports, the virtual machine might lose connection from the network. The error messages similar to the following might be written to the log files:

  2013-08-05T06:33:33.990Z| vcpu-1| VMXNET3 user: Ethernet1 Driver Info: version = 16847360 gosBits = 2 gosType = 1, gosVer = 0, gosMisc = 0
  2013-08-05T06:33:35.679Z| vmx| Msg_Post: Error
  2013-08-05T06:33:35.679Z| vmx| [msg.mac.cantGetPortID] Unable to get dvs.portId for ethernet0
  2013-08-05T06:33:35.679Z| vmx| [msg.mac.cantGetNetworkName] Unable to get networkName or devName for ethernet0
  2013-08-05T06:33:35.679Z| vmx| [msg.device.badconnect] Failed to connect virtual device Ethernet0.
  2013-08-05T06:33:35.679Z| vmx|

• PR 1136397: While updating the sensor data in the hardware status tab on an IBM x3650M3 server, Small Footprint CIM Broker (SFCB) core dumps from the ethernet provider is observed. The Hardware Status tab does not display data even after multiple attempts.
  
  
• PR 1138193: When PowerPath queries the CIM_System under /VMware/esxv2/, the operation fails and an error is reported from CIM server. The error is similar to the following:

  ThreadPool --- Failed to enqueue request. Too many queued requests already: vmwaLINUX
  ThreadPool --- Failed to enqueue request. Too many queued requests already: vmware_base, active 5, queued 11 .\TreeViewHostDiscovery.cpp 611

• PR 1140181: Simple Network Management Protocol (SNMP) creates trap files (.trp) in the /var/spool/snmp folder of ESXi host when the SNMP agent is stopped. When the directory /var/spool/snmp is not successfully deleted by SNMP agent is stopped, the hostd writes trap files (.trp) into /var/spool/snmp, causing the host to run out of inodes and appear as disconnected in vCenter Server. As a result, you might not be able to perform any task on the host.
  
  
• PR 1141175: The ESXi host becomes unresponsive and disconnects from vCenter Server. Also, the DCUI and SSH login to the host does not work due to memory leak in lsassd because of offline domains in Active Directory environment.
  
  
• PR 1142959: When 3D is enabled in the virtual machine settings, the user interface components of JavaFX application are not displayed correctly.
  
  
• PR 1145617: Host fails to apply NasStorageProfile and host is unable to leave maintenance mode during application failure.
  
  
• PR 1158766: When two virtual machines are configured with e1000 driver on the same vSwitch on a host, the network traffic between the two virtual machines might report significant packet drop in esxtop. This is happening because during the reporting there was no accounting for split packets when TSO is enabled from guest. The VMXNET3 network driver is updated in this release.
  
  
• PR 1160578: Virtual machines cannot reflect the serials numbers of the physical ESXi hosts.
  
  
• PR 1162062: RAM disk for SNMP traps is not created when the host is rebooted or restarting the management agents on an ESXi host from Direct Console User Interface. When an object is created in /var/spool/snmp (directory, file, link or other) of the ESXi host, then on starting SNMP service, RAM disk for SNMP traps is not created.
  
  
• PR 1166078: To disable cipher block chaining (CBC) algorithms for Payment Card Industry (PCI) compliance, you might need to disable weak ciphers on CIM port 5989. This is not permitted. You can update the configuration in sfcb.cfg to disable weak ciphers by running the following commands:
  
  

  # vi /etc/sfcb/sfcb.cfg
  sslCipherList: HIGH:!DES-CBC3-SHA
  # /etc/init.d/sfcbd-watchdog restart
  

• PR 1053302: When you attempt a VMware Tools update on an earlier ESXi 5.1.x, the vCenter Protect Agent displays a Unregistering VSS driver warning message, which indicates the use of an unsigned executable. Including the executable to the list of files copied to the install folder resolves this issue.
  
  
• PR 1053397: VMware Tools is updated to provide Oracle Linux 5.x with 2.6.39-200/400 prebuilt kernel modules.
  
  
• PR 1061656: When Receive Side Scaling is enabled on a multi vCPU Windows virtual machine, you see NetPort messages for repeating MAC addresses indicating that ports are being disabled and then re-enabled. In the vmkernel.log , you see messages similar to the following:
  
  2013-07-08T06:11:58.158Z cpu4:337203)NetPort: 1424: disabled port 0x1000020
  2013-07-08T06:11:58.177Z cpu4:337203)NetPort: 1237: enabled port 0x1000020 with mac xx:xx:xx:xx:xx:xx
  2013-07-08T06:12:46.191Z cpu1:337203)NetPort: 1424: disabled port 0x1000020
  2013-07-08T06:12:46.211Z cpu7:337203)NetPort: 1237: enabled port 0x1000020 with mac xx:xx:xx:xx:xx:xx
  
  The vmware.log file of virtual machines that use these MAC addresses contain corresponding events similar to the following:
  
  2013-07-08T06:18:20.175Z| vcpu-1| Ethernet4 MAC Address: xx:xx:xx:xx:xx:xx
  2013-07-08T06:18:20.199Z| vcpu-1| VMXNET3 user: Ethernet4 Driver Info: version = 833450 gosBits = 2 gosType = 2, gosVer = 24848, gosMisc = 212
  2013-07-08T06:18:36.165Z| vcpu-6| Ethernet4 MAC Address: xx:xx:xx:xx:xx:xx
  2013-07-08T06:18:36.187Z| vcpu-6| VMXNET3 user: Ethernet4 Driver Info: version = 833450 gosBits = 2 gosType = 2, gosVer = 24848, gosMisc = 212

  The VMXNET3 network driver is updated in this release.

• PR 1095083: When Receive Side Scaling is enabled on a multi vCPU Windows virtual machine, you see NetPort messages for repeating MAC addresses indicating that ports are being disabled and then re-enabled. In the vmkernel.log , you see messages similar to the following:
  
  2013-07-08T06:11:58.158Z cpu4:337203)NetPort: 1424: disabled port 0x1000020
  2013-07-08T06:11:58.177Z cpu4:337203)NetPort: 1237: enabled port 0x1000020 with mac xx:xx:xx:xx:xx:xx
  2013-07-08T06:12:46.191Z cpu1:337203)NetPort: 1424: disabled port 0x1000020
  2013-07-08T06:12:46.211Z cpu7:337203)NetPort: 1237: enabled port 0x1000020 with mac xx:xx:xx:xx:xx:xx
  
  The vmware.log file of virtual machines that use these MAC addresses contain corresponding events similar to the following:
  2013-07-08T06:18:20.175Z| vcpu-1| Ethernet4 MAC Address: xx:xx:xx:xx:xx:xx
  2013-07-08T06:18:20.199Z| vcpu-1| VMXNET3 user: Ethernet4 Driver Info: version = 833450 gosBits = 2 gosType = 2, gosVer = 24848, gosMisc = 212
  2013-07-08T06:18:36.165Z| vcpu-6| Ethernet4 MAC Address: xx:xx:xx:xx:xx:xx
  2013-07-08T06:18:36.187Z| vcpu-6| VMXNET3 user: Ethernet4 Driver Info: version = 833450 gosBits = 2 gosType = 2, gosVer = 24848, gosMisc = 212

  The VMXNET3 network driver is updated in this release.

• PR 1114634: You might be unable to run Petrel 3D application for oil and gas explorations correctly on a virtual machine due to issues with OpenGL graphics driver.
  
  
• PR 1123091: When you are saving files from a Microsoft Office 2007 or Microsoft Office 2010 application to a shared directory on a virtual machine protected by VMware vShield Endpoint and an agentless antivirus solution, you see errors similar to the following:
  
  

  File is currently in use. Try again later.
  Cannot save the file to this location.

  Files saved to the share are empty and 0KB in size.

• PR 1125220: When you run a vmtoolsd query such as vmtoolsd --cmd "info-get guestinfo.ovfEnv", the VMware Tools service might fail. This issue is known to occur on VMware Tools versions 9.0.1 and 9.0.5.
  
  
• PR 1130590: While upgrading the VMware Tools in Windows 8 and Windows 8.1 virtual machines, the user is automatically logged out of the virtual machines.
  
  
• PR 1162026: An error similar to the following might be displayed while updating an earlier version of VMware Tools to version 9.0.5 in a RHEL 6.2 (Red Hat Linux Enterprise) virtual machine using RPM (Red Hat Package Manager):

  Error: Package: kmod-vmware-tools-vsock-9.3.3.0-2.6.32.71.el6.x86_64.3.x86_64 (RHEL6-isv)
  Requires: vmware-tools-vsock-common = 9.0.1
  Installed: vmware-tools-vsock-common-9.0.5-1.el6.x86_64 (@/vmware-tools-vsock-common-9.0.5-1.el6.x86_64)
  vmware-tools-vsock-common = 9.0.5-1.el6
  Available: vmware-tools-vsock-common-8.6.10-1.el6.x86_64 (RHEL6-isv)
  vmware-tools-vsock-common = 8.6.10-1.el6
  Available: vmware-tools-vsock-common-9.0.1-3.x86_64 (RHEL6-isv)
  vmware-tools-vsock-common = 9.0.1-3

  
  
• PR 1033806: This patch updates the rste VIB to resolve the issue in which RSTe (Rapid Storage Technology enterprise) driver does not validate the NAA (Network Address Authority) ID reported by the disk and forwards an invalid ID to the upper layer.
  
  
• PR 1086706: This patch updates the net-e1000e VIB to resolve the issue in which the Intel e1000e network interface driver might stop responding on received (RX) traffic.
  
  
• PR 1110165 : When you install or reboot after installing the mpt2sas driver on Atmos hardware (Intel s2600jf, LSI 9200-8e) with ESXi 5.5, it might result in a purple diagnostic screen.
  
  
• PR 1006864: This patch updates the mpt2sas, lsi_msgpt3, mtip32xx_native, ahci, and megaraid_sas drivers. For the update to take effect you also need to install the ESXi550-201403201-UG bulletin.
  
  
• PR 1141761: This patch updates the sata-ahci VIB to update the ahci drivers.
  
  
• PR 1087070, 1127325: This patch updates the net-igb VIB to update the net_igb driver.
  
  
• PR 1196425: This patch updates the net-tg3 VIB to resolve the issue when the TSO capability is enabled in tg3 driver, the tg3 NICs might corrupt the data going through them. The TSO capability is disabled for tg3 NICs.

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 Installing and Administering VMware vSphere Update Manager.

ESXi hosts can be updated by manually downloading the patch ZIP file from the VMware download page and installing the VIB by using the esxcli software vib command. Additionally, the system can be updated using the image profile and the esxcli software profile command. For details, see the vSphere Command-Line Interface Concepts and Examples and the vSphere Upgrade Guide.