Allow pre-allocation of HugePages for WSL2

[Andarwinux]

For traditional Hyper-V VMs, it is possible to enable HugePages allocation for a VM using Set-VMMemory -HugePagesEnabled, but it is not possible to do so for WSL2. Considering that WSL2 memory is dynamically allocated, to avoid fragmentation, it is best to allow users to specify a fixed size of HugePages that will be allocated and never freed at WSL2 startup.

[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'.

[Andarwinux]

/feature

[github-actions]

Diagnostic information

Found '/feature', adding tag 'feature'