diff --git a/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md b/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md index 36070967178848bd5be294e2bca663c650937f3a..25b05c6be5821608c74e06741dcc6a59cab43675 100644 --- a/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md +++ b/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md @@ -227,25 +227,44 @@ Open a Terminal (_Applications -> System Tools -> Terminal_). Run all the follow Allow incoming X11 graphics from the compute nodes at the login node: +Get an interactive session on a compute node (for more detailed info [look here][4]). Forward X11 system using `X` option: + +```console +$ qsub -I -X -A PROJECT_ID -q qprod -l select=1:ncpus=36 +``` + +Test that the DISPLAY redirection into your VNC session works, by running an X11 application (e.g. XTerm, Intel Advisor, etc.) on the assigned compute node: + ```console -$ xhost + +$ xterm ``` -Get an interactive session on a compute node (for more detailed info [look here][4]). Use the `-v DISPLAY` option to propagate the DISPLAY on the compute node. In this example, we want a complete node (16 cores in this example) from the production queue: +The example described above: + + + +### GUI Over VNC and SSH +For the [better performance][1] an ssh connection can be used. + +Open two Terminals (_Applications -> System Tools -> Terminal_) as described before. + +Get an interactive session on a compute node (for more detailed info [look here][4]). Forward X11 system using `X` option: ```console -$ qsub -I -v DISPLAY=$(uname -n):$(echo $DISPLAY | cut -d ':' -f 2) -A PROJECT_ID -q qprod -l select=1:ncpus=16 +$ qsub -I -X -A PROJECT_ID -q qprod -l select=1:ncpus=36 ``` -Test that the DISPLAY redirection into your VNC session works, by running an X11 application (e.g. XTerm) on the assigned compute node: +In the second terminal connect to the assigned node and run the X11 application ```console +$ ssh -X node_name.barbora.it4i.cz $ xterm ``` + The example described above: + - [b]: http://www.tightvnc.com [c]: http://sourceforge.net/apps/mediawiki/tigervnc/index.php?title=Main_Page diff --git a/docs.it4i/img/node_gui_sshx.png b/docs.it4i/img/node_gui_sshx.png new file mode 100644 index 0000000000000000000000000000000000000000..267e863b2dabc1d0aad3e0f470cac4c2958fbb91 Binary files /dev/null and b/docs.it4i/img/node_gui_sshx.png differ diff --git a/docs.it4i/img/node_gui_xwindow.png b/docs.it4i/img/node_gui_xwindow.png new file mode 100644 index 0000000000000000000000000000000000000000..37401d03b3184c444ad40dab0465e4bad3539fd3 Binary files /dev/null and b/docs.it4i/img/node_gui_xwindow.png differ diff --git a/docs.it4i/software/debuggers/intel-vtune-profiler.md b/docs.it4i/software/debuggers/intel-vtune-profiler.md index dccd872ad121fc555e0892c5072b060bfc7bac7a..e0bec4276308e789ef8304e1758172bc0fef0bb4 100644 --- a/docs.it4i/software/debuggers/intel-vtune-profiler.md +++ b/docs.it4i/software/debuggers/intel-vtune-profiler.md @@ -25,6 +25,8 @@ To profile an application with VTune Profiler, special kernel modules need to be $ qsub -q qexp -A OPEN-0-0 -I -l select=1,vtune=2020_update3 ``` +For VTune/2022.2.0-intel-2021b use `vtune=2022_2_0` parameter. + After that, you can verify that the modules `sep*`, `pax`, and `vtsspp` are present in the kernel: ```console