Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Network I/O performance regression after migrating from bnx2x driver to qfle3 driver (52044)

Last Updated: 11/8/2023Categories: InformationalTotal Views: 17897Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

When you upgrade from VMware ESXi 6.5 to 6.7, you experience the below symptoms:

Qlogic E3 NIC driver migrates from bnx2x to qfle3 driver.

You experience performance regression, i.e higher CPU utilization, lower throughput in some cases.

OR

You see below PSOD on ESXi 6.7 host:

0x451a8f99bc20:[0x4180291533dd]FastSlab_AllocWithTimeout@vmkernel#nover+0x41 stack: 0x451a8f99bd68, 0x451a8f99bcb8, 0x451a8f99bd60, 0x430eba573560, 0x430eba6afda0
0x451a8f99bc70:[0x41802903c445]vmk_PageSlabAlloc@vmkernel#nover+0x22 stack: 0x451a00002400, 0x418000000000, 0x451a8f99bd00, 0x2400, 0x430eba573560
0x451a8f99bc80:[0x4180291cdfda]PktPageAlloc_AllocPages@vmkernel#nover+0x37 stack: 0x451a8f99bd00, 0x2400, 0x430eba573560, 0x430eba6affa0, 0x459aea403a30
0x451a8f99bd00:[0x4180292589cb]vmk_PktAllocPage@vmkernel#nover+0x10 stack: 0x430eba584c08, 0x4180299db709, 0xc04eac000, 0x2400, 0x430eba573560
0x451a8f99bd10:[0x4180299dbf51]qfle3_page_alloc_and_map@(qfle3)#<None>+0x22 stack: 0xc04eac000, 0x2400, 0x430eba573560, 0x26b, 0x430eba573560
0x451a8f99bd60:[0x4180299f05a5]qfle3_alloc_rx_sge_mbuf@(qfle3)#<None>+0x2e stack: 0x3, 0x1000, 0x0, 0x25bc, 0x430eba57e020
0x451a8f99bda0:[0x4180299f2164]qfle3_rxeof@(qfle3)#<None>+0x13d5 stack: 0x451a8f99be80, 0x418029226fbc, 0x1, 0x418029226ad3, 0x451a8f99bf00:[0x4180299f7d1e]qfle3_netpoll_rxcb@(qfle3)#<None>+0x21b stack: 0x8000000000001054, 0x4300d0db2680,

Cause

This issue occurs due to the difference in data path mechanism: bnx2x supports queue-paring mode, while qfle3 does not. As the result, qfle3 consumes more MSI-X vectors in data path, which in turn causes higher system overhead. Because of the lack of queue-paring mode, networking Load balance is also unable to consolidate traffic in netqueue.

Resolution

To resolve this issue please upgrade qfle3 driver to 1.0.84.0 or later.

ESX6.5: https://customerconnect.vmware.com/web/vmware/details?downloadGroup=DT-ESXI65-QLOGIC-QFLE3-1.0.88.0&productId=614
ESX6.7: https://customerconnect.vmware.com/web/vmware/details?downloadGroup=DT-ESXI67-QLOGIC-QFLE3F-10680&productId=742

To workaround this issue on VMware ESXi 6.x:

1. Disable qfle3 driver and enable bnx2x driver by running the below commands:

esxcli system module set --enabled=true --module=bnx2x
esxcli system module set --enabled=false --module=qfle3

2. Reboot the ESXi host.

Note: VMware ESXi 6.7 image is shipped with both bnx2x and qfle3 drivers.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant