Wsl/Service/RegisterDistro/CreateVm/HCS/E_INVALIDARG error during import on high-spec server (512GB RAM, Dual-Socket CPU)/在高配置物理服务器（双路 CPU，512GB 内存）上使用 wsl --import 导入发行版时，系统报错：Wsl/Service/RegisterDistro/CreateVm/HCS/E_INVALIDARG

[Robert-Descartes]

Windows Version

10.0.19045.7291

WSL Version

2.7.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.114.1-microsoft-standard-WSL2

Distro Version

Ubuntu-24.04

Other Software

No response

Repro Steps

1. On a Windows 10 machine with ≥512GB RAM and Hyper-V enabled:
   / 在拥有 ≥512GB 内存且启用 Hyper-V 的 Windows 10 机器上：

wsl --import Ubuntu-24.04 D:\wsl D:\ubuntu.tar --version 2
wsl --import Ubuntu-24.04 D:\wsl D:\ubuntu.tar --version 1

### Expected Behavior

installation success for both cases

### Actual Behavior

for wsl2:
Wsl/Service/RegisterDistro/CreateVm/HCS/E_INVALIDARG
for wsl1, installation success

### Diagnostic Logs

VirtualMachinePlatform: Enabled
Microsoft-Hyper-V-All: Enabled
HypervisorPlatform: Disabled

When importing a WSL2 distribution on a Windows 10 Pro machine with 524GB of RAM and 2 CPUs, the import operation fails with:

> Wsl/Service/RegisterDistro/CreateVm/HCS/E_INVALIDARG

The error does not occur if `.wslconfig` is explicitly configured 
with a reasonable memory limit.

在拥有 524GB 内存和 2 个 CPU 的 Windows 10 Pro 机器上导入 WSL2 发行版时，导入操作失败，错误信息为上述 `E_INVALIDARG`。当显式地在 `.wslconfig` 中配置合理的内存限制后，错误消失。

**.wslconfig**
   ```ini
   [wsl2]
memory=64GB
processors=64
swap=8GB
localhostForwarding=true

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[chemwolf6922]

Hi @Robert-Descartes , Please follow the steps the bot provided to share the log. Thanks.
In the meantime. Could you please try change the RAM and processors settings separately to see which option caused the problem (or both)? Thanks.
WSL currently does not support NUMA nodes. However it should not crash because of this.