Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TODO] Distribute Kernel Modules & Headers as VHD #114

Open
Locietta opened this issue Feb 15, 2025 · 2 comments
Open

[TODO] Distribute Kernel Modules & Headers as VHD #114

Locietta opened this issue Feb 15, 2025 · 2 comments
Labels
UPSTREAM Related to upstream changes or issues

Comments

@Locietta
Copy link
Owner

Locietta commented Feb 15, 2025

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).

Upstream: microsoft/WSL#12586

@Locietta Locietta added the UPSTREAM Related to upstream changes or issues label Feb 15, 2025
@Andarwinux
Copy link
Contributor

Andarwinux commented Feb 15, 2025

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..

@Locietta
Copy link
Owner Author

I'm thinking to add those less often used features as modules, something like #99. I'm not sure whether there are enough such features though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UPSTREAM Related to upstream changes or issues
Projects
None yet
Development

No branches or pull requests

2 participants