Problem
When using nsys CLI for profiling, a .nsys-rep report is not generated successfully.
Instead, profiling produces only a .qdstrm file and reports an importer error.
Steps to Reproduce
$ nsys profile --trace=cuda --output=report ./test
...
Collecting data...
Generating '/tmp/nsys-devcontainer/nsys-report-f8d1.qdstrm'
Importer error status: An unknown error occurred.
Unable to retrieve the importer version: skipping importation of the QDSTRM file.
Generated:
/current_working_dir/report.qdstrm
Environment
| Item |
Value |
| OS |
Ubuntu |
| Feature |
nsight-systems-cli |
| Feature Version |
1.0.1 |
| Nsight Systems Version |
2026.3.1.157-263138048394v0 |
Expected Behavior
nsys profile should successfully generate a .nsys-rep report.
Actual Behavior
Only a .qdstrm file is generated, and the import step fails with the following error:
Importer error status: An unknown error occurred.
Unable to retrieve the importer version: skipping importation of the QDSTRM file.
Impact
The generated .qdstrm file cannot be directly consumed by most CLI workflows, requiring manual import in the Nsight Systems UI.
This also prevents post-processing with commands such as:
nsys stats report.nsys-rep
Proposed Fix
Ensure that QdstrmImporter is available on $PATH.
For example:
cd /opt/nvidia/nsight-systems-cli/2026.3.1/host-linux-x64
ls -l
The devcontainer feature should append this directory to the PATH environment variable so that nsys can invoke QdstrmImporter during report generation.
For example,
https://github.com/devcontainers/features/pull/162/changes
References
Problem
When using
nsysCLI for profiling, a.nsys-repreport is not generated successfully.Instead, profiling produces only a
.qdstrmfile and reports an importer error.Steps to Reproduce
$ nsys profile --trace=cuda --output=report ./test ... Collecting data... Generating '/tmp/nsys-devcontainer/nsys-report-f8d1.qdstrm' Importer error status: An unknown error occurred. Unable to retrieve the importer version: skipping importation of the QDSTRM file. Generated: /current_working_dir/report.qdstrmEnvironment
nsight-systems-cli1.0.12026.3.1.157-263138048394v0Expected Behavior
nsys profileshould successfully generate a.nsys-repreport.Actual Behavior
Only a
.qdstrmfile is generated, and the import step fails with the following error:Impact
The generated
.qdstrmfile cannot be directly consumed by most CLI workflows, requiring manual import in the Nsight Systems UI.This also prevents post-processing with commands such as:
Proposed Fix
Ensure that
QdstrmImporteris available on$PATH.For example:
cd /opt/nvidia/nsight-systems-cli/2026.3.1/host-linux-x64 ls -lThe devcontainer feature should append this directory to the
PATHenvironment variable so thatnsyscan invokeQdstrmImporterduring report generation.For example,
https://github.com/devcontainers/features/pull/162/changes
References