fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

@oleksis @chrissicool

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)

@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`

@kernellogger @chrissicool How revert/apply the patch from the mailing related with `kernel/dma/swiotlb.c` ?

@kernellogger @chrissicool
Fixed applying/reverting the patch to kernel/dma/swiotlb.c

```bash
cd linux/sources/
curl -LJO github.com/torvalds/linux/comm
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 🙏🏾