Does version 2.6.3 of WSL still not support multiple NUMA nodes?

[luoxiaopiaoye]

Windows Version

Windows: 10.0.22621.4317

WSL Version

2.6.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Ubuntu 24.04.3 LTS

Other Software

lightgbm 4.6.0

Repro Steps

When I was training with LightGBM, I noticed that even though I had specified njobs=192, it seems that WSL can still only use one NUMA node and cannot utilize all system resources. Can this be configured?
Do I need to provide other information to identify the problem, or is the current version like this?

Information displayed in lscpu:
Virtualization features:
Virtualization: AMD-V
Hypervisor vendor: Microsoft
Virtualization type: full
Caches (sum of all):
L1d: 3 MiB (96 instances)
L1i: 3 MiB (96 instances)
L2: 48 MiB (96 instances)
L3: 16 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-191

<img width="506" height="357" alt="Image" src="https://github.com/user-attachments/assets/d62b3d30-754a-4120-b95b-9481f9e72db1"

Expected Behavior

I'm on WSL, and I can't seem to find the relevant settings in the config file either.

Actual Behavior

When training a large dataset with 900,000 rows using lightgbm, it is unable to utilize all CPU cores.

Diagnostic Logs

No response

[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-networking-logs.ps1, 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'.

[luoxiaopiaoye]

/question I recorded these logs during LightGBM training, which include the process from the non-training state to the training state
[WslLogs-2026-01-03_13-53-43.zip](https://github.com/user-attachments/files/24414049/WslLogs-2026-01-03_13-53-43.zip

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'
.wslconfig found
Detected appx version: 2.6.3.0