If you’re running Windows Server 2012 R2, I recommend using the new Powershell Get/Set-NetAdapterVMQ commands. Microsoft, Dell, and numerous other hardware/software vendors have confirmed the issue and suggested workarounds. For many users the solution seems to be a workaround to disable VMQ for all Broadcom network interfaces and teams in the system. There is a potential to resolve the issue with driver and firmware updates if a fix has been released by your hardware manufacturer. Problem showed up ONLY under network load (robocopy command, seeding new file server from old file share across network).īroadcom / QLogic NIC’s on Hyper-V servers can cause significant network performance issues for both the host and guest virtual machines. ADVANCED NIC SETTINGS showed BOTH VMQ AND FLOW CONTROL were enabled within the NIC driver – DISABLING BOTH resolved the issue for us immediately on this system. Get-NetAdapterVmq reported $False for all NICS.
Latest Dell OMSA (OpenManage Server Administrator GUI) reported healthy system (no critical firmware updates needed).
Broadcom network adapter drivers when vmq update#
UPDATE May 2016, seeing similar problem in the wild this year with NEW Dell PowerEdge R730 server Broadcom/QLogic 1Gbe NIC, Server 2012 R2 OS. did not help … disabled VMQ on all interfaces using PowerShell … Since then the issue is gone.” User over on reports that the issue persists with newer 10G Broadcom/QLogic NIC’s. UPDATE August 2017, following this issue as it’s in my top 10 most viewed posts.