VMMQ (Virtual Machine Multiple Queues) is a network-interface-card (NIC) capability that extends Receive Side Scaling (RSS) to virtual ports. On supported Hyper-V systems, the NIC can distribute incoming virtual-machine traffic across multiple receive queues and CPU cores instead of concentrating processing on one core. The result can be better receive-side scalability and less host CPU work, but only when the NIC, driver, Windows configuration and workload support it.
How VMMQ works
RSS balances receive processing across several logical processors. VMMQ applies that model to the virtual ports (VPorts) used by virtual machines and can offload packet-distribution work to compatible NIC hardware. Microsoft describes this as an NIC-side offload of the distribution function performed by virtual RSS (vRSS) in Hyper-V synthetic networking.
VMMQ is therefore a receive-path feature, not a general speed setting. A system with only one processing unit cannot benefit from RSS balancing, as Intel notes in its Ethernet Adapters and Devices User Guide (revision 29.5, November 12, 2024).
Why administrators use it
- Spreads incoming VM traffic over multiple queues and processors.
- Reduces host CPU work by moving queue-distribution tasks to the NIC when hardware offload is available.
- Helps virtualized workloads scale beyond a single receive-processing core.
These are design goals, not a guaranteed throughput increase. The available documentation does not establish one current benchmark result that applies to every adapter, driver, Windows release or workload.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems#1 Best Overall
What must support VMMQ
Hardware and driver
VMMQ depends on NIC hardware and its Windows driver. NVIDIA’s WinOF-2 documentation lists ConnectX-4, ConnectX-4 Lx and ConnectX-5 families in its documented support context. That support statement applies to the specified NVIDIA environment and should not be generalized to all adapters.
Operating system and network mode
NVIDIA documents VMMQ for Windows Server 2016 and later in Ethernet mode, not IPoIB. Other vendors can have different requirements, defaults and supported releases.
Rank #2
Virtual-switch and vendor policies
Queue availability can be affected by the Hyper-V virtual switch, adapter teaming, the number of virtual ports and vendor-specific policy. Cisco’s VIC 1400 guidance, for example, uses adapter and multi-queue policies in UCS Manager or IMC.
How to enable VMMQ on a Hyper-V adapter
Use the procedure and feature names documented for your exact NIC and driver. NVIDIA’s example requires virtual RSS (vRSS) to be enabled before VMMQ.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Confirm that the server is running a supported Windows Server release, the NIC is in a supported Ethernet configuration, and its driver and firmware expose VMMQ.
- Enable vRSS for the virtual machine network adapter according to your vendor’s instructions.
- In an elevated PowerShell session, enable VMMQ on the adapter by replacing the name with the adapter’s actual name:
Set-VMNetworkAdapter -Name "Virtual Adapter Name" -VmmqEnabled $true - If needed, request a number of queue pairs:
Set-VMNetworkAdapter -Name "Virtual Adapter Name" -VmmqQueuePairs <number> - Verify the resulting configuration with the Hyper-V and NIC management tools supplied for your Windows and driver versions, then measure the workload rather than assuming a gain.
The -VmmqQueuePairs value is a request, not a guarantee. NVIDIA states that Windows can decline or reduce the requested count because of available resources and other factors.
Vendor differences you should expect
| Implementation | Documented details | How to interpret them |
|---|---|---|
| NVIDIA WinOF-2 | Windows Server 2016 and later; Ethernet mode; ConnectX-4, ConnectX-4 Lx and ConnectX-5 families; vRSS required before VMMQ; PowerShell settings for VMMQ and queue pairs. | Applies to NVIDIA’s listed hardware, driver and mode. Queue-pair requests can be reduced by Windows. |
| Cisco VIC 1400 | Cisco reports VMMQ not enabled by default on Windows Server 2016 in its documented setup, while its Windows Server 2019 setup supports VMMQ by default. Its guidance describes one transmit queue and multiple receive queues, up to eight per VPort, with UCS adapter and multi-queue policies. | Cisco’s defaults and queue limits are configuration-specific, not universal Windows behavior. |
| Intel Ethernet guidance | Defines VMMQ as RSS for virtual ports attached to a physical port and notes that RSS has no effect on a one-processing-unit system. | Use the Intel guide for the capabilities and controls of the specific Intel adapter and driver. |
What to check before troubleshooting
- Exact NIC model, firmware and Windows driver version.
- Windows Server release and whether the vendor enables VMMQ by default.
- Ethernet versus another network mode; NVIDIA’s cited support statement is Ethernet-only.
- Whether vRSS is enabled before VMMQ.
- Available queue resources, number of VPorts and the queue count Windows actually grants.
- Hyper-V switch, teaming and vendor policy requirements.
- Whether the workload has enough receive traffic and CPU parallelism to benefit.
Common misconceptions
“VMMQ is a universal Windows switch.”
No. The control may be exposed only when the NIC and driver support it, and vendor defaults differ.
“The requested queue count is the active queue count.”
No. It is a requested value; operating-system resource limits can result in fewer queues.
“Enabling VMMQ guarantees faster networking.”
No. VMMQ targets receive-side scaling and CPU efficiency. Actual results depend on hardware, driver, VM count, traffic pattern and host resources, so validate with measurements from your own workload.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Choosing compatible hardware
If you are selecting a server Ethernet adapter for VMMQ, look for explicit VMMQ support in the vendor’s documentation and verify the exact model, driver, firmware, Windows Server release and server platform. A family name alone is not proof that every board, mode or driver combination supports the feature. VMMQ is a specialist infrastructure capability, not a requirement for understanding or running ordinary virtual machines.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
