How to Configure Hyper-V Resource Pools in Windows 11 Using PowerShell

In dense virtualisation environments, managing hardware resource allocation on a per-virtual machine basis can quickly become unwieldy and introduce resource starvation. Hyper-V Resource Pools in Windows 11 provide an administrative framework to aggregate, partition, and govern physical system resources—including logical processors, memory, virtual switches, and virtual hard disks. Through PowerShell cmdlets dedicated to resource pooling, system administrators can enforce collective resource quotas, isolate testing environments from production workloads, and streamline cluster capacity management.

Understanding Hyper-V Resource Pool Architecture

Hyper-V implements resource pools across several fundamental infrastructure types:

• Processor Pools: Regulate maximum CPU limits, reserve percentages, and relative weights across assigned virtual machines.
• Memory Pools: Group system RAM to ensure that specific virtual machines draw from designated NUMA nodes or pre-allocated physical memory boundaries.
• Ethernet Pools: Aggregate virtual network switches to route guest traffic through isolated virtual adapters or enforced bandwidth profiles.
• VHD / Storage Pools: Bind groups of virtual hard disks to specific storage tiers, paths, or IOPS quotas.

Every Hyper-V host possesses default parent resource pools for each subsystem. Administrators can build custom child resource pools beneath the root pools to implement compartmentalised resource tiers.

Inspecting Existing Resource Pools

Before creating custom resource pools, inspect the baseline pools automatically maintained by the Hyper-V hypervisor. Launch PowerShell with elevated administrator privileges:

# List all default and custom Hyper-V resource pools
Get-VMResourcePool

# Inspect pools filtered by specific resource type
Get-VMResourcePool -ResourcePoolType Processor
Get-VMResourcePool -ResourcePoolType Memory
Get-VMResourcePool -ResourcePoolType Ethernet

Notice the Primordial pool. Primordial pools represent the host’s complete unpartitioned physical capacity from which custom child pools draw their allocations.

Creating Custom Processor and Memory Resource Pools

To establish a bounded compute environment—such as a developer test ring that must not exceed half the host’s compute capacity—create dedicated child pools using New-VMResourcePool.

# Create a dedicated processor resource pool
New-VMResourcePool -Name "Dev-CPU-Pool" -ResourcePoolType Processor

# Create a dedicated memory resource pool
New-VMResourcePool -Name "Dev-Memory-Pool" -ResourcePoolType Memory

Once created, configure resource constraints, weights, and minimum reserve limits on the pool using Set-VMResourcePool or by modifying parent allocation parameters:

# Verify newly provisioned child pools
Get-VMResourcePool -Name "Dev-*" | Select-Object Name, ResourcePoolType, ParentPoolName

Creating and Binding Ethernet Virtual Switch Pools

Ethernet resource pools allow multiple virtual switches to be grouped into a logical network fabric. When a virtual machine connects to an Ethernet pool, Hyper-V dynamically binds the VM’s virtual network interface to an available switch within that pool.

# Identify existing virtual network switches
Get-VMSwitch | Select-Object Name, SwitchType, NetAdapterInterfaceDescription

# Create a custom Ethernet resource pool
New-VMResourcePool -Name "Internal-Tier-Pool" -ResourcePoolType Ethernet

# Bind specific virtual switches to the Ethernet resource pool
Set-VMResourcePool -Name "Internal-Tier-Pool" -ResourcePoolType Ethernet -Paths "vSwitch-Internal-1", "vSwitch-Internal-2"

Creating Storage VHD and ISO Pools

Storage pools aggregate target disk paths and virtual hard drive directories. This prevents virtual machine provisioners from placing virtual disk files on unmonitored host volumes:

# Create a storage pool for high-speed NVMe storage
New-VMResourcePool -Name "NVMe-Storage-Pool" -ResourcePoolType VHD

# Add host storage directories to the VHD pool
Set-VMResourcePool -Name "NVMe-Storage-Pool" -ResourcePoolType VHD -Paths "D:\VMStorage\Tier1", "E:\VMStorage\Tier1"

Assigning Virtual Machines to Custom Resource Pools

With resource pools established, assign virtual machine hardware components to the target pool. Configurations apply to the virtual hardware objects of the guest machine:

1. Assigning Processor Resource Pools

# Bind virtual machine processor to the custom CPU pool
Set-VMProcessor -VMName "DevBox-01" -ResourcePoolName "Dev-CPU-Pool"

# Verify processor pool assignment
Get-VMProcessor -VMName "DevBox-01" | Select-Object VMName, ResourcePoolName

2. Assigning Memory Resource Pools

# Bind virtual machine memory to the custom memory pool
Set-VMMemory -VMName "DevBox-01" -ResourcePoolName "Dev-Memory-Pool"

# Verify memory pool assignment
Get-VMMemory -VMName "DevBox-01" | Select-Object VMName, ResourcePoolName

3. Assigning Network Adapters to Ethernet Pools

# Connect guest network adapter to the Ethernet resource pool
Get-VMNetworkAdapter -VMName "DevBox-01" | Set-VMNetworkAdapter -PoolName "Internal-Tier-Pool"

# Verify network adapter pool association
Get-VMNetworkAdapter -VMName "DevBox-01" | Select-Object VMName, Name, PoolName

Auditing Resource Consumption Across Pools

Resource pools integrate seamlessly with Hyper-V Resource Metering to track compute and network consumption across multi-tenant boundaries. Enable metering directly on custom pools:

# Enable resource metering for the CPU and Memory pools
Enable-VMResourceMetering -ResourcePoolName "Dev-CPU-Pool" -ResourcePoolType Processor
Enable-VMResourceMetering -ResourcePoolName "Dev-Memory-Pool" -ResourcePoolType Memory

# Measure real-time consumption across the pool
Measure-VMResourcePool -Name "Dev-CPU-Pool"
Measure-VMResourcePool -Name "Dev-Memory-Pool"

The output reports aggregate CPU utilization, allocated memory thresholds, and average usage statistics for all machines assigned to the pool.

Modifying and Deleting Resource Pools

Before removing a custom resource pool, ensure that no virtual machines or network adapters are currently assigned to it. If necessary, revert virtual machines to the default Primordial pool:

# Reassign virtual machine back to default primordial pool
Set-VMProcessor -VMName "DevBox-01" -ResourcePoolName $null
Set-VMMemory -VMName "DevBox-01" -ResourcePoolName $null

# Remove the custom resource pool
Remove-VMResourcePool -Name "Dev-CPU-Pool" -ResourcePoolType Processor
Remove-VMResourcePool -Name "Dev-Memory-Pool" -ResourcePoolType Memory

Leveraging Hyper-V Resource Pools in Windows 11 establishes structured multi-tenant boundaries, prevents rogue workloads from destabilising host hardware, and streamlines ongoing hypervisor maintenance.