This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
When trying to start Hyper-V machines configured wit 4096 MB memory and 2 CPUs running W11 24H2 I get this error message:
'MyVirtualMachine' failed to start worker process: The target device has insufficient resources to complete the operation. (0x80070142). (Virtual machine ID 72BBF752-959A-4CAD-8A78-9457CCBEB9EC)
Both worked flawlessly with W10 and W11 23H2.
Any idea how to cope with this fault.
The log show the reason for this Error: "Virtual machine 'CD5C185DA0A52A0A-00-00.mrimg' 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 1E580B01-F14A-4CFE-B66F-FFDAA2EACA6E)"
This is definitively a bug in Host 24H2 Hyper-V, because the Host (W11 24H2) and the client (W100 23H2) are both W11 machines which does support or even use NUMA.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 88%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERF%3C/text%3E%3C/svg%3E)
Hi, go to hyper-v settings and enable numa spanning.
I had to reboot after changing. Just restarting the service was not enough or I did it at the wrong service.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 94%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIX%3C/text%3E%3C/svg%3E)
Hi Jorg,
Thanks for your post. Can I know if you have turned on NUMA spanning in Hyper-V settings after upgrading? NUMA spanning means Hyper-V will allocate memory from other remote physical NUMA nodes if the memory requirements for the virtual machine cannot be satisfied from a single node. Refer to this link for more details.
Best Regards,
Ian Xue
If the Answer is helpful, please click "Accept Answer" and upvote it.
Hi IAN,
setting NUMA spanning did the trick. I have flagged the post accordingly. This is a little surprising, because NUMA is neither supported by Windows 11 Client nor available on my Mainboard. So this setting is definitively a workaround to overcome a severe bug.