You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Latest WSL2 6.6.y kernel update provides instructions for bundle kernel module files into a VHD. But they don't give any details about how to use the generated modules.vhdx. I'm expecting WSL2 team will give us some options in .wslconfig and it will just work out of box.
If so, we can easily implement kernel update with modules via scoop. Users don't have to update kernel module files manually for each distro & each release, which is nice. We don't have to build everything into the kernel then.
Also it's not difficult to bundle kernel headers as a VHD too, it will be more convenient for people who somehow need original kernel headers (e.g. to develop kernel drivers on WSL2).
I do find some instructions to mount VHDX manually via PowerShell/WSL commands, but this requires per-distro setup (e.g., fstab, partition mounting).
I still prefer to have everything built-in in order to get fully covered LTO and CFI, but bundled headers are very useful indeed.
Incidentally, Fuchsia Clang will soon be built with PGO, which is expected to reduce kernel build times by 20%, which alleviates the need to modularize the kernel for build time reasons..
Latest WSL2 6.6.y kernel update provides instructions for bundle kernel module files into a VHD. But they don't give any details about how to use the generated
modules.vhdx
. I'm expecting WSL2 team will give us some options in.wslconfig
and it will just work out of box.If so, we can easily implement kernel update with modules via scoop. Users don't have to update kernel module files manually for each distro & each release, which is nice. We don't have to build everything into the kernel then.
Also it's not difficult to bundle kernel headers as a VHD too, it will be more convenient for people who somehow need original kernel headers (e.g. to develop kernel drivers on WSL2).
Upstream: microsoft/WSL#12586
The text was updated successfully, but these errors were encountered: