I use Windows computer comes with NsighjtSystem2023.1.2 can SSH connection WSL2 and run the program, but will report the error does not match with CUDA12.4, when to re-download 2024.4.1, will show the connection WSL2, please ask how to solve：
Subject: Need Help with Nsight System Version Compatibility
After testing on my computer, I’ve found that I can only use Nsight System versions 2023.3.1, 2023.2.1, and 2023.1.1. Versions after 2024.1.1 are not available/accessible.
I suspect this might be due to software configuration settings, but I haven’t been able to identify the exact cause. Has anyone encountered similar issues or have suggestions for troubleshooting? Any help would be greatly appreciated!
Is there any reason that you can’t move to a more recent CTK/Nsys?
I tested Nsight 2025.3.1, and it’s also failing to work properly under the current setup. I think my main problem is that with the previous version of Nsight using SSH I can connect to Linux, and when I use the latest Nsight I can’t connect to my device
@liuyis do you have any suggestions?
@Heijun Is it possible for you to use Nsys CLI in WSL? I’m not sure if GUI connection to WSL is tested well.
Nsight Systems cannot be used directly within WSL. To work around this, I installed Nsight Systems on the Windows 11 host in order to connect to WSL. Interestingly, this setup worked with versions prior to 2024. However, starting from the 2024 release, I can no longer connect to WSL, and the issue persists even with the latest 2025 version.
Nsight Systems cannot be used directly within WSL.
That’s no longer the case today. Nsys CLI can be used in WSL, but for CUDA trace you need a config option to WAR time conversion issue. See Release Notes — nsight-systems 2025.3 documentation
Interestingly, this setup worked with versions prior to 2024. However, starting from the 2024 release, I can no longer connect to WSL, and the issue persists even with the latest 2025 version.
Nsys GUI support for WSL is not well tested, so there might be some bug in latest versions. The suggestion for now is to use Nsys CLI in WSL directly and copy report back to a different system to view it. If GUI remote profiling for WSL is an important use case for you, we can file a bug for it.
After carefully implementing your suggested approach—including installing the latest Nsys version in WSL and verifying all recommended configurations—I regret to report that the issue persists. Specifically, I encountered the following error during profiling:
CUDA device 0: Unified Memory cannot be traced on devices that don’t support peer-to-peer transfers.Please verify that SLI/NVLink is functioning properly.
[image]
System configuration:
NVIDIA Nsight Systems version 2025.3.1.90-253135822126v0
CuptiUseRawGpuTimestamps=false
Hi @Heijun, does other features work except this error message? This “error” is kind of as expected because the underlying feature is not supported on WSL.