#WSL 1.1.7 is now available to Windows Insiders and among others bumps the #LinuxKernel to the #Linux 6.1 (a longterm aka LTS #kernel)
https://github.com/microsoft/WSL/releases/tag/1.1.7
[edit: They released 1.2.0 shortly after and reverted to a 5.15.y kernel to "debug a few issues": https://github.com/microsoft/WSL/releases/tag/1.2.0 ; thx to @chrissicool for mentioning it in a reply]
@kernellogger @chrissicool From using the custom linux kernel >= 6.3-rc4 getting some errors related with Network.
Some advices?
https://gist.github.com/oleksis/ada196eaeb43e1a6fe85a4d2e50f6b21
I’m using the lasts source kernel Linux 6.3 (rc-4 and rc-5) with the config from the WSL2 branch 6.1.y https://github.com/microsoft/WSL2-Linux-Kernel/blob/1c07cedf3b7c290862175601e8eee2caabc1e895/Microsoft/config-wsl
1/2
@kernellogger @chrissicool I was able to using the kernel source until 6.3-rc3 with this config https://github.com/oleksis/wsl2-linux-kernel-config/blob/855f555a3a90495a8c0c5a6b48d9925ec22db2bf/Microsoft/config-wsl
2/2
no idea, sorry; you might want to report this upstream (and check if it was reported already) if you are pretty sure that it's not something local that causes this: if 6.3-rc3 worked and 6.3-rc4 fails it's a regression that should be fixed (hence CC the regressions list)
/me wonders if https://lore.kernel.org/all/20230405003549.GA21326@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/ might be related (but the commit was merged after rc4)
@kernellogger @chrissicool i compile the Linux kernel 6.3-rc4, days after the release using your guide with git. One week later I try 6.3-rc5 with the config 5.15.90.1 and 6.1.21.1 and keep getting the error `Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/E_UNEXPECTED`
that's a error msg from windows, I have no clue what it means.
But if -rc4 worked and -rc5 failed it's likely the same problem as https://lore.kernel.org/all/CAA42JLa1y9jJ7BgQvXeUYQh-K2mDNHd2BYZ4iZUz33r5zY7oAQ@mail.gmail.com/
@kernellogger @chrissicool How revert/apply the patch from the mailing related with `kernel/dma/swiotlb.c` ?
there are many texts on the web that explain how to apply a patch or undo a commit, please consult those.
FWIW, https://docs.kernel.org/next/admin-guide/quickly-build-trimmed-linux.html briefly mentions it, too
@kernellogger @chrissicool
Fixed applying/reverting the patch to kernel/dma/swiotlb.c
```bash
cd linux/sources/
curl -LJO https://github.com/torvalds/linux/commit/0eee5ae1025699ea93d44fdb6ef2365505082103.patch
git apply -R 0eee5ae1025699ea93d44fdb6ef2365505082103.patch
➜ uname -a
Linux Laptop 6.3.0-rc5-oleksis-microsoft-standard-WSL2+ #1 SMP Wed Apr 5 22:03:41 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux
```
@oleksis @kernellogger @chrissicool
I got the same networking error with a custom 6.7 kernel built from the latest torvalds/linux sources. The patch seems to have been merged upstream already so not sure what I should do.
```
Failed to configure network (networkingMode Nat). To disable networking, set `wsl2.networkingMode=None` in C:\Users\theo\.wslconfig
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/E_UNEXPECTED
```
@theoparis@chrissicool@mastodon.social
If the problem @oleksis faced was solved upstream (it was, wasn't it?) I'd assume it's just similar symptom due to a totally different problem
@theoparis @kernellogger @chrissicool I will give a new try… Please let us know how the problem was resolved