Skip to content

config-wsl: CONFIG_INFINIBAND disabled in 6.18.58.1 kernel, breaking RDMA and Soft-RoCE #42255

Open

Description

Windows Version

Microsoft Windows [Version 10.0.26200.9911]

WSL Version

3.0.5.0

Are you using WSL 1, WSL 2, or WSLC?

  • WSL 2
  • WSL 1
  • WSLC

Kernel Version

6.18.58.1-microsoft-standard-WSL2

Distro Version

Ubuntu 24.04.5 LTS (Noble Numbat)

Other Software

rdma-core 50.0-2ubuntu0.2
iproute2 6.1.0-1ubuntu6.4

Repro Steps

  1. Install or update to WSL 3.0.5.0, which includes kernel 6.18.58.1.

  2. Start a WSL 2 distribution.

  3. Run:

    uname -r
    grep '^CONFIG_INFINIBAND=' /boot/config-$(uname -r)
    modinfo rdma_rxe
  4. Compare the WSL kernel configurations:

The 6.18.33.2 configuration contains CONFIG_INFINIBAND=m. In 6.18.58.1 it was changed to # CONFIG_INFINIBAND is not set.

Expected Behavior

The WSL kernel should retain CONFIG_INFINIBAND=m, as it did in kernel 6.18.33.2, so RDMA applications and ABI-matched external RDMA modules can work.

It would also be useful for the standard WSL kernel to provide CONFIG_RDMA_RXE=m for Soft-RoCE support.

Actual Behavior

WSL 3.0.5.0 uses kernel 6.18.58.1, where CONFIG_INFINIBAND is disabled.

As a result, the InfiniBand/RDMA core is unavailable and Soft-RoCE cannot be used. rdma_rxe is not included in the standard kernel, and an external ABI-matched RXE module cannot load without the required RDMA core support.

This worked with our previous WSL environment based on kernel 6.18.33.2, where CONFIG_INFINIBAND=m was enabled.

Diagnostic Logs

Current output:

WSL version: 3.0.5.0
Kernel version: 6.18.58.1-1
Windows version: 10.0.26200.9911
Distribution: Ubuntu 24.04.5 LTS

$ uname -r
6.18.58.1-microsoft-standard-WSL2

$ grep '^CONFIG_INFINIBAND=' /boot/config-$(uname -r)
<no output; option is unset>

$ modinfo rdma_rxe
modinfo: ERROR: Module rdma_rxe not found.

The upstream config-wsl files linked in the reproduction steps show the configuration regression directly.

Activity

  1. github-actions commented on Nov 12, 2026

    @github-actions
    Contributor

    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 script will output the path of the log file once done.

    If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

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

    See Collect WSL logs (recommended method).

    If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

  2. sbenmelech commented on Nov 12, 2026

    @sbenmelech
    Author

    This is critical for Azure Boost next Gen (Overlake 4) as currently we work purely on simulators based on WSL and have no other way to develop / test without RXE support.

  3. OneBlue commented on Nov 12, 2026

    @OneBlue
    Collaborator

    Mitchell Levy (@chessturo): Can we bring this back in the next kernel (potentially as module) ?

  4. sbenmelech commented on Nov 13, 2026

    @sbenmelech
    Author

    Hi Blue (@OneBlue) , Mitchell Levy (@chessturo) , Sorry to nudge but it seems some of our devboxes started to get WSL updates and now blocking development (or forcing to downgrade every other day).
    Is there a way to expedite this?
    Thanks!

  5. Ziy1-Tan commented on Nov 15, 2026

    @Ziy1-Tan

    Restoring CONFIG_INFINIBAND (this issue) does not give Soft-RoCE. CONFIG_RDMA_RXE has never been set in any WSL kernel, so modprobe rdma_rxe fails with Module rdma_rxe not found.

    Requested in arch/x86/configs/config-wsl:

    CONFIG_RDMA_RXE=m
    

    No new dependency chain: INET, PCI, NET_UDP_TUNNEL are already set, INFINIBAND_VIRT_DMA comes with IB core. Ship the .ko in artifacts.vhd too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

kconfiglinux kernel configurationwsl2Issue/feature applies to WSL 2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions