Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

VMware ESXi 5.0, Patch ESXi500-201212204-UG: Updates VMware ESXi 5.0 net-ixgbe vib (2033756)

Release Date: December 20, 2012

Patch Category	Bug Fix
Patch Severity	Important
Build	For build information, see KB 2033751.
Host Reboot Required	Yes
Virtual Machine Migration or Shutdown Required	Yes
Affected Hardware	N/A
Affected Software	N/A
VIBs Included	VMware:net-ixgbe_2.0.84.8.2-11vmw.500.2.26.914586
PRs Fixed	860684, 900239
Related CVE numbers	N/A

For more information on patch and update classification, see KB 2014447.

Summaries and Symptoms

This patch updates the net-ixgbe VIB to resolve the following issues:

PR 860684: When you try to enable flow control on the Intel 82599EB Gigabit Ethernet controller, the ixgbe driver incorrectly sets the flow control mode to priority-based flow control in which the flow control is always disabled. As the result, the error message Cannot set device pause parameters: Invalid argument appears when you try to enable flow control.
PR 900239: When you install X520-DA2 network interface card with ixgbe driver on HP DL580 server ESX host fails with a purple screen. This happens because of the delay in programming of VLAN filter on ixgbe driver of a physical network interface card.

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.

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

1 2 3 4 5
0 Ratings

1 2 3 4 5
0 Ratings

Actions

KB:

Did this article help you?
This article resolved my issue. This article did not resolve my issue. This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)