[WSL2 6.6.87.2] VA-API initialization segfaults in `vaInitialize` with AMD 680M (Radeon 24.9.1 driver)

[ardenbin-bit]

Windows Version

Microsoft Windows [版本 10.0.22631.5335]

WSL Version

WSL 版本: 2.6.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2

Distro Version

Ubuntu 24.04

Other Software

When trying to enable hardware-accelerated video transcoding (via VA-API) in WSL2, the vainfo utility consistently segfaults during library initialization. This prevents any application (like Immich) from using GPU acceleration.

• WSL2 Kernel Version / 内核版本: 6.6.87.2-microsoft-standard-WSL2
• Windows Build / Windows 版本: Windows 11 (Please provide your winver output)
• Linux Distro / Linux 发行版: Ubuntu 24.04 (Noble)
• GPU / 显卡: AMD Radeon 680M (integrated)
• Windows GPU Driver / Windows 显卡驱动: AMD Adrenalin 24.9.1 (WHQL)
• WSLg / 图形支持: Enabled via guiApplications=true in .wslconfig

Repro Steps

1. In a WSL2 Ubuntu terminal, install VA-API tools: sudo apt install vainfo mesa-va-drivers
2. Run vainfo.

Expected Behavior

vainfo should list the AMD GPU and supported codecs (H.264, HEVC, etc.).

Actual Behavior

vainfo outputs libva info: VA-API version 1.20.0 and then crashes with Segmentation fault (core dumped).

Diagnostic Logs

1. GPU Passthrough is Working / GPU直通工作正常:

   • /dev/dri/ directory exists with renderD128 device after running sudo modprobe vgem.
   • DXGKRNL module is loaded (/sys/module/dxgkrnl exists).

2. Permissions are Correct / 权限正确:

   • User is in video and render groups.

3. Crash Point Identified / 崩溃点已确认:

   • strace and ltrace pinpoint the crash to the vaInitialize() function call.
   • Relevant ltrace output / 相关 ltrace 输出:

     vaGetDisplayWl(0x62007c7e4370, 0, 0, 529)        = 0x62007c7e9850
     vaInitialize(0x62007c7e9850, 0x7fff1acf8ccc, 0x7fff1acf8cc8, 5libva info: VA-API version 1.20.0
      <no return ...>
     --- SIGSEGV (Segmentation fault) ---
     

4. All VA-API Backends Tested / 所有 VA-API 后端均已测试:

   • Tried LIBVA_DRIVER_NAME=radeonsi, d3d12, iHD, i965. All result in the same segfault.

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

If this is a networking issue, please use collect-networking-logs.ps1, 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'.

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

[MatthewTeta]

I'm seeing the same issue. Logs included below:

WslLogs-2026-04-08_16-45-54.zip

I've just run vainfo and seen the following output:
libva info: VA-API version 1.20.0 Segmentation fault (core dumped)