Hi All,
We have ESX5.0 installed on a couple of HP BL460C G7 blade servers. Having faced issues during VMotion and having gone through the community discussions/recommendations, we upgraded the nic firmware as well as the be2net driver to the recommended levels:
~ # ethtool -i vmnic0
driver: be2net
version: 4.2.327.0
firmware-version: 4.1.450.16
bus-info: 0000:02:00.0
~ # ethtool -i vmnic1
driver: be2net
version: 4.2.327.0
firmware-version: 4.1.450.16
bus-info: 0000:02:00.1
However, during the last couple of times we have rebooted the esx host we have seen it get stuck on a panic and enter the vm kernel debugger. I am attaching a screenshot of the stack trace in case anyone is interested or has some pointers regarding the stability of this driver version 4.2.327.0. Sorry if the image is not of the best quality/resolution. If any extra info is needed to root-cause, I'd be glad to try and get that.
Am interested to know if we are missing any updates/fixes further to the driver update or if this is a known issue (some firmware incompatibility) or cause for alarm.
Thanks,
Anand