When hosting high-throughput virtual machines on Windows 11—such as local Kubernetes nodes, database test benches, or intensive development virtual environments running on Microsoft Hyper-V—network throughput can become severely constrained if network packet processing is restricted to a single virtual CPU core. While Virtual Machine Queue (VMQ) technology allocates dedicated hardware packet queues to separate virtual machines, traditional VMQ binds all inbound traffic for an individual VM to one single logical processor. To distribute incoming network packet processing across multiple virtual processors simultaneously, Windows incorporates Virtual Machine Multiple Queues (VMMQ). Using PowerShell, administrators can query hardware support, enable VMMQ, and tune queue allocations.
Understanding Virtual Machine Multiple Queues (VMMQ)
VMMQ builds upon Virtual Machine Queue (VMQ) and Receive Side Scaling (RSS) technologies. In traditional VMQ, the physical network adapter uses hardware MAC address and VLAN filtering to place inbound packets into a dedicated queue assigned to a specific VM. However, the host operating system processes that queue on a single physical CPU core, which caps the VM’s network throughput at the processing capacity of that single core.
Virtual Machine Multiple Queues (VMMQ) overcomes this bottleneck by assigning multiple hardware queues to a single virtual machine network adapter. Inbound traffic is dynamically spread across these queues using Receive Side Scaling (RSS) hashing. As a result, packet processing is distributed across multiple virtual processors assigned to the virtual machine, allowing a single guest VM to achieve multi-gigabit throughput on 10 GbE, 25 GbE, and faster physical network adapters.
Verifying Hardware and Switch Support in PowerShell
VMMQ requires physical network adapters that support VMQ and multi-queue RSS offloading. Open an elevated PowerShell session (Run as Administrator) and inspect the hardware capabilities of your physical network adapters:
Get-NetAdapterVmq
To inspect whether your virtual switches support VMMQ offloading, query the VmqSettingData via the Hyper-V namespace:
Get-VMSwitch | Select-Object Name, SwitchType, NetAdapterInterfaceDescription
To check the current offload configuration of virtual machine network adapters across all Hyper-V virtual machines on the system, run:
Get-VMNetworkAdapter -All | Select-Object VMName, Name, VmmqEnabled, VmmqQueuePairs, VrfDefaultQueuePairs
If VmmqEnabled is set to False, the virtual network adapter is currently restricted to single-queue packet processing.
Enabling VMMQ on Virtual Machine Network Adapters
You can enable VMMQ on a specific virtual machine network adapter while the VM is stopped or running (depending on the guest integration service level):
Set-VMNetworkAdapter -VMName "Ubuntu-Dev" -VmmqEnabled $True
To configure the number of hardware queue pairs allocated to the virtual machine, pass the -VmmqQueuePairs parameter:
Set-VMNetworkAdapter -VMName "Ubuntu-Dev" -VmmqEnabled $True -VmmqQueuePairs 4
Allocating 4 queue pairs allows the network stack to distribute inbound traffic across 4 distinct virtual CPUs inside the guest operating system, preventing core saturation during heavy continuous data transfers.
Configuring VMMQ for the Host Default vSwitch Adapter
If you use Hyper-V Virtual Switch sharing where the host operating system accesses the physical network through a virtual adapter (management operating system adapter), enabling VMMQ on the host virtual adapter dramatically accelerates host file sharing and container routing.
To enable VMMQ on the host virtual adapter:
Set-VMNetworkAdapter -ManagementOS -VmmqEnabled $True -VmmqQueuePairs 4
To verify the updated configuration on the management adapter:
Get-VMNetworkAdapter -ManagementOS | Format-List Name, VmmqEnabled, VmmqQueuePairs
Configuring Physical Adapter RSS and VMQ Base Processors
To ensure that physical CPU cores are not overloaded by overlapping VMQ queues, fine-tune the base processor and queue distribution on the physical network adapter:
Set-NetAdapterVmq -Name "Ethernet 1" -BaseProcessorNumber 2 -MaxProcessors 8
This configuration instructs the network driver to avoid CPU 0 and CPU 1 (reserving them for operating system kernel interrupts and scheduling routines) and spreads VMQ interrupts across logical processors 2 through 9.
Monitoring VMMQ Performance and Queue Distribution
To verify that traffic is actively distributing across multiple queues during high-bandwidth testing, monitor real-time queue statistics using PowerShell:
Get-NetAdapterVmqQueue -Name "Ethernet 1" | Select-Object QueueId, MacAddress, VlanId, Processor, QueueType
You will observe multiple QueueId entries assigned to the same virtual machine MAC address, each mapped to a distinct processor core. This distribution confirms that VMMQ is actively parallelising packet processing across host and guest CPU cores.
Disabling VMMQ for Diagnostic Troubleshooting
If you encounter packet jitter or driver conflicts on older hardware adapters that have limited hardware queue table space, disable VMMQ on the target VM:
Set-VMNetworkAdapter -VMName "Ubuntu-Dev" -VmmqEnabled $False
The adapter immediately reverts to standard single-queue VMQ operation, ensuring backward compatibility while preserving virtual machine network connectivity.