Kernel in 2.3.11 no longer monolithic?

[polyzen]

Windows Version

Microsoft Windows [Version 10.0.19045.4651]

WSL Version

2.3.11

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.36.3

Distro Version

Arch Linux

Other Software

usbipd-win

Repro Steps

1. usbipd.exe attach --wsl --hardware-id 'blah'
2. Receive error saying WSL kernel is not USBIP capable, due to cat /sys/devices/platform/vhci_hcd.0/status failing
3. sudo modprobe vhci-hcd
4. usbipd.exe attach --wsl --hardware-id 'blah'
5. Device attaches

Expected Behavior

Module already loaded

Actual Behavior

Try to attach USB device, find the vhci-hcd module needs to be loaded:
dorssel/usbipd-win#995

Diagnostic Logs

No response

[polyzen]

From usbipd-win dev:

BTW: it worthwhile noting thay CONFIG_USBIP_HOST=m makes absolutely no sense. It used to be # CONFIG_USBIP_HOST is not set. WSL can never be a USB host. There is no physical USB, and the Linux USBIP subsystem does not allow forwarding client USB devices.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• Feature request: Support for loadable kernel modules (#10450), similarity score: 0.72

Closed similar issues:

• usbip oraclelinux79 error opening vhci_driver (#9705), similarity score: 0.73
• Can't Attach USB Devices to WSL (#9990), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[polyzen]

Can provide the logs the bot requested, but not sure if they're necessary here.

[elsaco]

@polyzen are you using systemd? The vhci_hcd modules loads okay on a distro with systemd=true but won't load on a non-systemd distro. In fact no modules would load on a non-systemd WSL distro.

Look in /lib/modules/6.6.36.3-microsoft-standard-WSL2/kernel/drivers/usb/usbip and you'll find vhci-hcd.ko module.

ubuntu@eleven:~$ modinfo vhci-hcd
filename:       /lib/modules/6.6.36.3-microsoft-standard-WSL2/kernel/drivers/usb/usbip/vhci-hcd.ko
license:        GPL
description:    USB/IP 'Virtual' Host Controller (VHCI) Driver
author:         Takahiro Hirofuchi
depends:        usbcore,usbip-core,usb-common
retpoline:      Y
intree:         Y
name:           vhci_hcd
vermagic:       6.6.36.3-microsoft-standard-WSL2 SMP preempt mod_unload modversions

Looks like modules are mounted by:

ubuntu@eleven:~$ systemctl list-units --type=mount
  UNIT                                                            LOAD   ACTIVE SUB     DESCRIPTION                                      
  ---cut---
  usr-lib-modules-6.6.36.3\x2dmicrosoft\x2dstandard\x2dWSL2.mount loaded active mounted /usr/lib/modules/6.6.36.3-microsoft-standard-WSL2
  ---cut---

[polyzen]

Yes, this is with systemd. Maybe you misread, but I was able to load the module.

[polyzen]

#11789 (comment)