Nsys fail to caputure gpu kernel

Developer Tools Nsight Systems Profiling Linux Targets
1

I’m using Nsight Systems 2026.2.1 on Windows, and Nsight Systems 2026.2.1 CLI inside WSL2.

In WSL2, I run:

nsys profile -o v1_cuda --trace=cuda -f true /home/xbs/INFRA/project1/engine_inferrence/build/yolov11 /home/xbs/INFRA/project1/engine_inferrence/engine/static_batch_yolov11.engine /home/xbs/INFRA/project1/engine_inferrence/test/3.jpg

Then I open the generated v1_cuda file in the Windows Nsight Systems GUI, but no GPU kernel activities show up at all.
I saw a related solution from 2024 suggesting to adjust the nsys-config.ini file, but that did not work for me.below is oral post.

Does anyone have a reliable fix or troubleshooting steps to get GPU kernel tracing working in WSL2 with Nsight Systems?

2

@skottapalli do you have any thoughts?

3

Okay, I’ve fixed this issue. The method given in the link works perfectly. I have no idea why it failed the first time I tried it, but I remembered this matter today and tried it again, and it worked out. Anyway, thanks a lot for your help.

4

Still, I’m wondering something. That workaround was put forward back in 2024, and it comes at the cost of reduced accuracy. It’s already been two years, so haven’t there been any new improvements or better solutions released by now?