Can't activate distro with custom kernel built with WSL2-Linux_Kernel Project

[Fang-GotATaste]

Windows Version

Microsoft Windows [version 10.0.26100.2033]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

I don't know. "wsl.exe --status" return: "default distro:docker-desktop-data default version:2"

Distro Version

Ubuntu 22.04 LTS

Other Software

Docker Desktop Windows,
"docker version" return "Version:25.0.3 Go version:1.21.6"
I don't know if its wanted and which helps.

Repro Steps

In wsl I do:
" git clone https://github.com/microsoft/WSL2-Linux-Kernel
cd WSL2-Linux-Kernel
cp Microsoft/config-wsl .config
sudo apt update
make menuconfig"
and success.

Then I configure in the menu:
I ""and"[ * ]" every options in "Network support"
and make the kernel.

I add "kernel=[address]"in file C:\Users\user.wslconfig and it works.

Then I shutdown wsl and try activate the distro.

Expected Behavior

the distro will be activated then I will do"make modules_install"

Actual Behavior

the distro can't activate and the terminal just flash and disappear.(I use WSL Manager)
If i change kernel address in C:\Users\user.wslconfig to target the old kernel, the distro work normally(at least outwardly).It doesn't work in any custom kernel I bulit. I try a few times making in configurations as above.

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 here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• Custom kernel not being recognized. (#11779), similarity score: 0.72
• wsl2: fail to launch custom linux kernel on ARM64 devices through replacing file under lxss/tools/kernel (#4896), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[Fang-GotATaste]

WslLogs-2024-10-17_18-52-41.zip

[github-actions]

Diagnostic information

.wslconfig found
	Custom kernel found: 'C:\Windows\System32\lxss\tools\kernel.old'
Detected appx version: 2.2.4.0
Detected user visible error: Wsl/Service/CreateInstance/CreateVm/WSAENOTCONN
Detected user visible error: Wsl/Service/CreateInstance/CreateVm/WSAENOTCONN