Forum Discussion
NUMA Problems after In-Place Upgrade 2022 to 2025
We have updated several Hyper-V hosts with AMD Milan processors from Windows 2022 to Windows 2025 using the in-place update method.
We are encountering an issue where, after starting about half of the virtual machines, the remaining ones fail to start due to a resource shortage error.
The host's RAM is about 70% free. We can only get them to start by enabling the "Allow Spanning" configuration, but this reduces performance, and with so many free resources, this shouldn't be happening.
Has anyone else experienced something similar? What has changed in 2025 to cause this issue?
The error is:
Virtual machine 'R*****2' cannot be started on this server. The virtual machine NUMA topology requirements cannot be satisfied by the server NUMA topology. Try to use the server NUMA topology, or enable NUMA spanning. (Virtual machine ID CA*****3-ED0E-4***4-A****C-E01F*********C4).
Event ID: 10002
<EventRecordID>41</EventRecordID>
<Correlation />
<Execution ProcessID="5524" ThreadID="8744" />
<Channel>Microsoft-Windows-Hyper-V-Compute-Admin</Channel>
<Computer>HOST-JLL</Computer>
4 Replies
Hi Friends,
I've also stumbled across this problem and found out that it's related to VBS and HVCI.
In other words, if you disable HVCI, which unfortunately is not possible on a Server 2025 on a permanent/persistent basis, at least I haven't found a way to do so yet, then disabling NUMA spanning, as with Hyper-V 2022, has no such negative effects.
Best Regards
Alex
Yes, the VM start without problem before the host migration. Right now the are started but with the "Allow Spanning" checked.
To help you further on this issue, can you please share below data for the host and VMs?
- SMT configuration of the host
- SMT configuration of the all of the VMs
- Number of VPs and memory foreach VM
For #1, Taskmgr output(of CPU view) on from the host such as below is sufficient.
For #2 and #3 please share VM configuration image from Hyper-V Manager for all the VMs
Thanks for providing above info towards further investigation on this issue.
Sorry to hear about your situation. Does these VMs use to start i.e. work in WS2022 i.e. before upgrade? If needed, are you able to provide us additional diagnostic information towards investigation? Thanks.
