Hyper-V: VMQ should be enabled on VMQ-capable physical network adapters bound to an external virtual switch

Hyper-V: VMQ should be enabled on VMQ-capable physical network adapters bound to an external virtual switch

This article is intended to provide more information about a specific issue that can be identified by running a Best Practices Analyzer scan for Hyper-V. It also can be used without running a scan, as general troubleshooting and best practice information to help you configure your server appropriately. If you have troubleshooting steps or information that would improve this article, please add it. For instructions on how to edit a TechNet Wiki article, see Wiki: How to Use the Editor.

For more information about best practices and scans, see Run Best Practices Analyzer Scans and Manage Scan Results.

Operating System

Windows Server 2012





Note: The following sections provide details about the specific issue. Italics indicates UI text that appears in the Best Practices Analyzer tool for the specific issue.


The following network adapters are capable of virtual machine queue (VMQ) but the capability is disabled.


Windows is unable to take full advantage of available hardware offloads on the following network adapters: \n{0}


Enable VMQ using the Enable-NetAdapterVmq Windows PowerShell cmdlet or using the Advanced Properties user interface for the network adapter.

Additional references


Sort by: Published Date | Most Recent | Most Useful
  • For me, enabling VMQ on a HP ML350 G8 w/ Broadcom NetXtreme quad-port NIC led to a massive performance penalty (PINGs to guest VMs occasionally reaching >250ms, w/o VMQ <= 1ms)

  • Same ping issues here with a DL360p gen8, excessive ping times when VMQ is enabled.

  • Same ping issue Dell R320. Latest firmware and Server 2012. Users on VM's battled to open files over the network until I disabled VMQ. Improvement was amazing.

  • Ditto.  Disable VMQ all was well this with Dell R720 Broadcom Nextreme

  • you might be seeing high pings because dynamic VMQ isn't working. Try manually settings the VMQ for each adapter See the following article: support.microsoft.com/.../2974384

    Also check NIC drivers are up to date!

Page 1 of 1 (5 items)