Hello All,
I need your help in troubleshooting degraded VDI workloads on AMD and Intel CPU servers. I suspect that Windows 11 does not play nicely with AMD CPU and possibly Intel as well. Need help making sense of this.
This is a virtualized ESX environment. Ever since upgrading VDI vms to Windows 11 performance has taken a serious hit with users reporting all types of lag/application freezing/mouse response delay/video rendering issues you name it.
The only change has been the Windows 10 ----> 11 upgrade. My troubleshooting has led me to suspect the trigger and issue is Memory Integrity/HVCI features. We conducted A/B tests to prove this.
Need your help in assessing if there is something at the CPU arch. level/GMET and how Windows 11 interacts with it causing the issue?
Environment & Products Involved
Hypervisor: ESXi 8.0.3 (Build 25595708)
Guest OS: Windows 11 (VDI desktops)
Virtual Hardware: Version 21+
VMware Tools: 12.5
Platforms:
Intel: Dell PowerEdge R640, Xeon Gold 6246R (Cascade Lake) — 2 sockets × 16 cores = 32 physical cores / 64 threads, SNC disabled (2 NUMA nodes)
AMD: Dell PowerEdge R6525, EPYC 74F3 (Milan / Zen 3) — 2 sockets × 24 cores = 48 physical cores / 96 threads
Workload: High-density VDI (Intel hosts typically 19–25 VMs / predominantly 4-vCPU; AMD hosts 15–16 VMs / predominantly 12-vCPU)
Storage controllers: LSI (emulated) on the VDI VMs
Security feature: Windows 11 Memory Integrity / HVCI (Hypervisor-Protected Code Integrity) under VBS — enabled by default on qualifying hardware
Timeline:
performance issues became visible after the upgrade from Windows 10 to Windows 11. Windows 10 supported HVCI but did not enable it by default. Windows 11 22H2+ enables Memory Integrity by default on hardware that meets the requirements (both platforms do). It seems the same host densities and ESXi configuration that were stable under Windows 10 began showing problems once the continuous HVCI overhead was introduced.
Troubleshooting (Using VMWARE ESXTOP to diagnose performance issues)
What Has Been Observed
Intel R640 hosts (16 cores/socket)
Severe NUMA memory locality degradation and continuous cross-socket rebalancing.
Multiple hosts show CRITICAL/WARNING NUMA findings (Ex. ESX had 12 CRITICAL; others had 5–9 CRITICAL warnings with NUMA thrashing).
Worst examples VM %Local averaging ~48 %, remote memory multi-gigabyte, rebalance count rising continuously (step-function migrations throughout the capture).
Per-node core utilization consistently high 70s to low 80s % with spikes near 100 %. (NUMA)
No %VMWAIT episodes and low per vCPU Ready / Co-Stop. Below 5%
Dashboard confirmation: both NUMA nodes under pressure, free memory ample (no swap/ballooning), locality fractured because page migration lags home-node changes.
AMD R6525 hosts (24 cores/socket)
NUMA placement remains healthy (zero or near-zero migrations, high %Local).
Recurrent %VMWAIT episodes (peaks 48–66 % on multi-vCPU VMs) with high wake rates (15k–24k/s during episodes vs ~1k/s outside).
Low vCPU Ready, Co-Stop, and disk latency.
Disabling HVCI eliminates the %VMWAIT episodes and has produced significant user-reported performance improvement.
Common across both
CPU Ready and Co-Stop stay within acceptable thresholds.
Classic resource exhaustion (memory pressure, storage latency, ready-time contention) is not the primary driver.
Hardware and ESXi meet VBS/Credential Guard prerequisites (Broadcom KB 447325): HW 21+, Tools 12.5, ESXi exposing MBEC (Intel) / GMET (AMD).
Suspected Primary Trigger
Windows 11 default enablement of Memory Integrity (HVCI).
Even with hardware acceleration (MBEC on Cascade Lake, GMET on Milan), HVCI adds continuous hypervisor exits, nested page-table activity, and execute-control checks. Under the existing densities this incremental cost was enough to:
On Intel (16 cores/socket): exhaust local cores during concurrent bursts → ESXi NUMA scheduler repeatedly rebalances across UPI → page migration (throttled to protect the interconnect) cannot keep up → fractured locality and remote-memory latency.
On AMD (24 cores/socket): leave VMs local but surface the same HVCI cost directly as %VMWAIT blocking.
The architectural difference (cores per socket) determines how the same HVCI overhead is expressed it seems. The OS upgrade is the change that made the latent density limit operationally visible.
Has anyone else encountered this issue or have any understanding as to what is happening at the CPU level? I have come across multiple Windows 11 HVCI/VBS performance related threads and forum posts so I am curious if anyone here has recently.
Any ideas or suggestion are appreciated thank you!