Out of the ten hosts I have with the cards, only two experienced the issue, and that was after about four weeks of uptime. Broadcom was able to produce the issue on Linux boxes and are now testing on Windows boxes. You are commenting using your Facebook account. This article resolved my issue. No, the advice is still to disable NetQueue as per above. Post was not sent – check your email addresses!
|Date Added:||19 September 2007|
|File Size:||8.82 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Inbox drivers are now included with ESXi 5. Expand VMkernel in the list and click Boot. The issue is resolved with the release of a new async i. No, the advice is still to disable NetQueue as per above.
Select your language
This has an advantage over unloading and re-loading the driver because this only affects a specific NIC at a time and not all NICs using the tg3 driver. You need to enable security on this component, as it could expose confidential information see Allowing User Impersonation. Seems that there is a updated driver for vSphere 4. I dont think VMware have this bug in their KM system ….
Hi, do you have any news on this? Broadcom was able to produce the issue on Linux boxes and are now testing on Windows boxes.
Did this article help you? Am now waiting for contact from Broadcom.
You can verify broadccom issue by unloading and reloading the tg3 driver by running these commands: Had notification of a new tg3 driver through via VUM on 21st December: Ridiculous that this is very dangerous bug is still unfixed. Thanks for keeping us updated. You are commenting using your WordPress.
VMware ESX/ESXi issues with Broadcom quad port Gb NIC | Robin CM’s IT Blog
There is now a VMware KB article about this which details the above workaround. Notify me of new posts via email.
I talked to a VMware tech a 2 days ago and he said Broadcom updated the ticket that VMware has with them about this issue. This article did not resolve my issue. View the contents of the esx. But you could anwser me a question. Is there an updated driver for this issue? This site uses Akismet to reduce spam. KB article addressing the issue but no mention of new driver: To work around this issue without upgrading the network driver, disable the NetQueue feature.
English Japanese Chinese Simplified.
Ensure to contact and confirm with your hardware vendor before upgrading to the driver versions mentioned in this article. Scroll down to the setting named VMkernel.
What can we do to improve this information?