Today, working at a customer deploying Hyper-V hosts with Emulex CNA1100 we run into issues (did not surprise me, since the issue have been around for more than a year, but I still try and test to see if it ever gets better).
The issue is that VMQ still needs to be disabled on every Emulex NIC. That bad thing is that the issue has been around for a very, very long time. It took a very long time for the vendor to acknowledge the issue and now they state that there is a solution soon to be released. I really hope that, but I have heard it before…
Read more here:
My simple recommendation is to disable VMQ in all Emulex Network adapters if they are installed in Windows Server 2012 R2 or buy something that works and use VMQ.
When they release something that actually works I will remove this blog post.
/m
Share this:
Categories: Hyper-V
The Deployment Bunny 
So what does work? :) It seems like people are reporting the same thing for Intel and Broadcom NICs, but maybe I’m wrong?
We have used Intel 520/540 Nic’s with no or minimal issues so far. We are also investigating if QLogic could work I have not used Broadcom for a long time.
The August 4th fix resolved the issue for us so far, 3 weeks with no disconnects.
That is great!, we still have varius issues with VMQ and Emulex in general, hope it will be solved in the future