This configuration was originally based on Clear Linux's kernel config options toned down for general kernel usage and enabled a number of scenarios some of which that are addressed in other simpler PRs. This should make it easier to troubleshoot the Hyper-V side for bringing support to some features. USBIP has been enabled as this is a known working scenario with use of extra software installed on both Windows and WSL2. Adds ExFAT, NTFS, and IPv6 support (still needs work on the VM side). This is part of the resolution to https://github.com/microsoft/WSL2-Linux-Kernel/issues/114. attn: @craigloewen-msft and @sashalevin

Update: Fixed OP to reflect current config changes.

fix tools/perf 3 bugs: 1 perf_env__arch return dangling pointer 2 normalize_arch function read out of bound when the arch is "i*86". 3 global variable like "the_var" defined in muliple files without "static" key word qualified, lead to linkage error.

This change enables the usage of the virtual vcan socketcan driver. This allows linux users to add a virtual socketcan device, and test programs which make use of socketcan in WSL2.

This configuration was originally based on Clear Linux's kernel config options toned down for general kernel usage and enabled a number of scenarios some of which that are addressed in other simpler PRs. This should make it easier to troubleshoot the Hyper-V side for bringing support to some features. USBIP has been enabled as this is a known working scenario with use of extra software installed on both Windows and WSL2. Adds ExFAT, NTFS, and IPv6 support (still needs work on the VM side). This is part of the resolution to #114. attn: @craigloewen-msft and @sashalevin. Options not supported in 5.4 should be ignored during compilation.

Enables a number of scenarios some of which are addressed in smaller PRs. USBIP has been enabled as this is a known working scenario with use of extra software installed on both Windows and WSL2. Adds ExFAT, NTFS, and IPv6 support. This should make it easier to troubleshoot the Hyper-V side for bringing support to some features. Improves the security posture and boosts performance of the kernel. Use bcc to compare the difference (Required kernel options are enabled in this PR). @craigloewen-msft and @sashalevin.

For use with the latest version, we need the updated config. This also can be used as a base to build the mainline version.

Solve issues:

microsoft/WSL#5366 microsoft/WSL#5481 #142

iptables conntrack doesn't work, even on the latest master branch.

$  iptables -A PREROUTING -t raw -p tcp --dport 21 -j CT
iptables: No chain/target/match by that name.

After some intensive digging, it looks like NETFILTER_XT_TARGET_CT is not enabled. Once enabled, the above works flawlessly.

dwarves package provides pahole without which build fails with

BTF: .tmp_vmlinux.btf: pahole (pahole) is not available
Failed to generate BTF for vmlinux
Try to disable CONFIG_DEBUG_INFO_BTF

Would your ms team upgrade the wsl2 kernel download packages address which still the old version 5.4 released in april 2021. Only kernel version above 5.10.43.3 will work on nvidia cuda. https://docs.microsoft.com/en-us/windows/wsl/install-manual

I am a wsl2 ML user just change win11 back to win10 ltsc 2022. As ms announced win10 21h2 support wsl gpu accelerated ml training , however the github release packages seem only some source code, and official download address still old one.

After several failed attempts make the kernel myself, I finally get your official release one in windows catalog. Wish all your efforts not just hidden in corner.

These are proposed edits made by @diddlesnaps to enable strict confinement of snap packages on WSL2.

Post on Snapcraft forum: https://forum.snapcraft.io/t/running-snaps-on-wsl2-insiders-only-for-now/13033

Ref WSL#4286. Aligns with stock Ubuntu kconfig. Brings back /proc/sys/kernel/yama/ptrace_scope which oddly enough is a WSL1 feature (ref microsoft/WSL#121).