![broadcom network adapter drivers when vmq broadcom network adapter drivers when vmq](https://c1.neweggimages.com/ProductImageCompressAll1280/A9AXS200217vJIeC.jpg)
Please note that if your network adapters are 1G, then disabling VMQ will have no effect since VMQ is disabled on the Hyper-V virtual switch for virtual machines that are using 1G network adapters.
#BROADCOM NETWORK ADAPTER DRIVERS WHEN VMQ UPDATE#
If you update the driver and the issue persists, or if you don’t want to update your network driver for some reason, you can alternatively disable VMQ (VM Queueing) on the Hyper-V host network adapter that is used by your Hyper-V virtual switch. However, in my experience, the driver update does not always resolve the issue. The issue is supposed to be resolved by updating your network adapter driver to a version greater than 16.8. The cause is an issue with an outdated Broadcom NetExtreme network adapter driver.
![broadcom network adapter drivers when vmq broadcom network adapter drivers when vmq](https://strikingly.gotorange.top/d/5.png)
Rebooting the Hyper-V host will resolve the issue temporarily, and the Hyper-V guest servers will operate normally for some time.
![broadcom network adapter drivers when vmq broadcom network adapter drivers when vmq](https://powenstupid.weebly.com/uploads/1/3/3/9/133978309/648430783_orig.jpg)
From my experience, the issue is typically triggered under a heavy network load on a virtual server, such as a large file transfer between two servers. Some of the virtual servers on the same Hyper-V host may not experience the network issue at all. What typically happens is that your Hyper-V guest virtual servers seem to have random networking issues. It especially crops up on HPe Proliant Servers. Experiencing odd network issues with Hyper-V guest virtual servers is an old issue, but it is one I still occasionally see.