The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
VMware ESXi 5.0, Patch ESXi500-201310203-UG: Updates VMware ESXi 5.0 misc-drivers vib (2055554)
Release Date: October 17, 2013
|Build||For build information, see KB 2055559.|
|Host Reboot Required||Yes|
|Virtual Machine Migration or Shutdown Required||Yes|
|VIBs Included||VMware: misc-drivers_5.0.0-3.41.1311175|
|PRs Fixed||922606, 981030|
|Related CVE numbers||N/A|
For more information on patch and update classification, see KB 2014447.
Summaries and Symptoms
This patch updates the misc-drivers VIB to resolve the following issues:
- PR 922606: When network traffic passes through the bnx2x device driver and the vmklinux receives the Large Receive Offload (LRO) generated packets, the network packets might be dropped resulting in the failure of the ESXi hosts with a purple screen. The ESXi hosts experience a divide-by-zero exception during the TSO split and finally results in failure of the host. This issue occurs when the bnx2x driver sends the LRO packet with a TCP Segmentation Offload (TSO) MSS value set to zero.
Also, the ESXi host fails when the packet received is invalid for any one of the following reasons:
- If the GSO size is zero
- If the GSO type is not supported
- The vLAN ID is incorrect
- PR 981030: When VMKlinux incorrectly sets the device status, false Device Busy (D:0x8) status messages are displayed in VMkernel log files similar to the following:
2013-04-04T17:56:47.668Z cpu0:4012)ScsiDeviceIO: SCSICompleteDeviceCommand:2311: Cmd(0x412441541f80) 0x16, CmdSN 0x1c9f from world 0 to dev "naa.600601601fb12d00565065c6b381e211" failed H:0x0 D:0x8 P:0x0 Possible sense data: 0x0 0x0 0x0
This generates false alarms as the storage array does not send any Device Busy status message for SCSI commands. This issue is resolved in this release by correctly pointing to Host Bus Busy (H:0x2) status messages for issues in the device drivers similar to the following:
2013-04-04T13:16:27.300Z cpu12:4008)ScsiDeviceIO: SCSICompleteDeviceCommand:2311: Cmd(0x4124819c2f00) 0x2a, CmdSN 0xfffffa80043a2350 from world 4697 to dev "naa.600601601fb12d00565065c6b381e211" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0
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.
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.