Skip to content

Commit 62bc766

Browse files
kelsey-steelechessturo
authored andcommitted
README.md: Include more details for modules with custom kernels
Added details about loadable modules being disabled when using a custom kernel with WSL2. While WSL2 can boot and run with the v6.6 configs and module support disabled, this may limit functionality for some users, such as running Docker. Advised users to set any needed modules to built-in (=y) before building their custom kernel. Suggested using the last v5.15 config to build the v6.6 kernel for those who prefer the previous configuration setup. Signed-off-by: Kelsey Steele <kelseysteele@microsoft.com>
1 parent 17fea4b commit 62bc766

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

README.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,13 @@ as follows:
3333
2. Modify WSL2 kernel configs (optional):
3434
`$ make menuconfig KCONFIG_CONFIG=Microsoft/config-wsl`
3535

36-
Loadable module support is disabled when using a custom built kernel. Set any modules you want to be built-in before building.
36+
When using a custom-built kernel, loadable module support is disabled.
37+
Configurations set as modules (=m) won’t be available. Set any needed modules
38+
to built-in (=y) before building your custom kernel.
39+
40+
If you prefer the old configuration before WSL introduced loadable module
41+
support, you can use the old config file from the linux-msft-wsl-5.15.y branch
42+
to build your v6.6 WSL2 kernel.
3743

3844
3. Build the kernel using the WSL2 kernel configuration:
3945
`$ make KCONFIG_CONFIG=Microsoft/config-wsl`

0 commit comments

Comments
 (0)