Jetson Xavier Nsight support

When testing the nsys-ui tool via an SSH session with X11 forwarding, no HDMI support, the tool fails with an error message which appears related to a missing Qt dependency. This is the same issue encountered when manually installing Nsight from the .deb files found in the SDK Manager. Are both nsys and nsys-ui supported on the Xavier? Or only nsys command line app?

root@MasterEdge:/home/rekor# nsys-ui
Warning: Failed to get OpenGL version. OpenGL version 2.0 or higher is required.
OpenGL version is too low (0). Falling back to Mesa software rendering.
MoTTY X11 proxy: Unsupported authorisation protocol
qt.qpa.xcb: could not connect to display localhost:10.0
qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: offscreen, wayland-egl, wayland, xcb.
################# ERROR: CrashReporter #################
CrashReporter
Qt initialization failed
Failed to load Qt platform plugin: “xcb”

  • Library path: /opt/nvidia/nsight-systems/2022.3.3/host-linux-armv8/Plugins/platforms/libqxcb.so
    Application is going to abort
    MoTTY X11 proxy: Unsupported authorisation protocol
    Error: Can’t open display: localhost:10.0
    /usr/local/bin/nsys-ui: line 52: 3992 Aborted (core dumped) “$NV_AGORA_PATH/CrashReporter” --hide-stack “NVIDIA Nsight Systems” “NsightSystems” “2022.3.3 (Build 2022.3.3.18-4d5367b)” “$NV_QUADD_PATH” “$@”

Hi,

Do you try to run Nsight on the device?
We expect users to run the profiler on a host machine and remote profile the device’s app.

Thanks.

Yes, first attempts were to run nsys-ui on the device. From the documentation, it appears that nsys command line version can be run on the device and the collected data can be analyzed elsewhere. I see that the CLI and host GUI versions must match to import .qdstrm files and that the host GUI is backward compatible only with .nsys-rep files.

I have not yet found the documentation on running the profile on a host machine and remote profiling. Our application that needs profiling runs in a Docker container. The attempts to run the CLI and GUI versions were both made from the device host outside of the docker container.

Hi,

Do you meet any issues when running the Nsight system CLI tool on Jetson? It’s expected to work.
You can find the compatible device and host package from the SDKmanager if the same JetPack version is selected.

Nsight system can profile an application by giving the target PID.
Is this sufficient for your use case?

Thanks.

Hi,

We just confirmed that nsys-cli can work within container.

For example:

$ sudo docker run -it --rm --net=host --runtime nvidia -e DISPLAY=$DISPLAY -v /tmp/.X11-unix/:/tmp/.X11-unix nvcr.io/nvidia/l4t-base:r35.1.0
# apt update
# apt-get install nsight-systems*
# nsys profile /usr/bin/dmesg 
WARNING: CPU sampling in a Docker container requires `--pid=host` Docker option or `--sampling-trigger=perf` NSys option, disabling.
WARNING: CPU sampling in a Docker container requires `--privileged=true` Docker option, disabling.
WARNING: 'timer' backtrace collection trigger will not be used because sampling is disabled.
WARNING: 'sched' backtrace collection trigger will not be used because sampling is disabled.
dmesg: read kernel buffer failed: Operation not permitted
Generating '/tmp/nsys-report-b0e4.qdstrm'
[1/1] [========================100%] report1.nsys-rep
Generated:
    /report1.nsys-rep

Thanks.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.