It's been happening for a while now. Several different hosts, dell hosts, using "QLogic 57810 10 Gigabit Ethernet Adapter" network cards have been failing for a while now while using the native qfle3 driver. We tried disabling the load balancing queues without any positive results (hosts kept crashing)- The only solution we found was to revert to bnx2i drivers. This definitely made the hosts sop crashing.

We are discarding hardware problems since it's been happening on multiple machines - even the hardware retailer agreed to replace some of those cards but no luck still. The version on the hosts is 6.7.0 and we are having a hard time getting a straight answer from VMWare - Frimwares are ok according to the compatibility matrix.

Did anyone else come across this issue? What could the problem be?

1 Answer 1


Edit 2019-03-01: Updated drivers have been released at VMware support portal.

I just spent 7 months working on this (or very similar?) issue with HPE, Broadcom/QLogic/Cavium/Marvell (whoever they are now...) and VMware. It's been tough and a very pink (as is PSODs) experience. It started in June 2018 to July 2018 in different datacenters with different configurations. As HPE requires you to use qfle3 and vSphere 6.0 (that is allowed to use bnx2) lacked some key functionality, I was between a rock and a hard place.

There are 2 independent issues (maybe more, but specific to my issue):

  • iSCSI offload (as you mention bnx2i) driver is unstable. I've heard various other accounts but in my case hosts would PSOD within seconds or minutes after configuring iSCSI (often resulting in bootloop as host would crash during boot iSCSI login). I have beta drivers from late December 2018 that work fine now. Stable/tested/qualified drivers are supposed to be published by Marvell at QLogic download portal at the end of January 2019 (or early February). Workaround: use software iSCSI.
  • There's a bug in vSphere 6.7 RSS module that should be fixed in vSphere 6.7U2 (spring 2019). This causes occasional PSODs, NMIs or just network connectivity loss (often a bit after vMotion). Workaround is to disable vSphere RSS loadbalancer esxcli network nic queue loadbalancer set --rsslb=disable -n vmnicX

In my case I had to switch all production NICs to Intel ones (that don't support iSCSI nor RSS) but I continued to push the case due to some future requirements.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.