Analyzers
Community support for Analyzers (Intel VTune™ Profiler, Intel Advisor, Intel Inspector)

GUI not loading

ShivamThukral
Beginner
1,074 Views

Hi, 

 I am having the following error while launching vtune-gui. The screen loads but it is blank. 

sthukral@LOCLAP385:/opt/intel/oneapi/vtune/latest/bin64$ sudo ./vtune-gui
[300686:0221/114710.604514:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[300686:0221/114710.604588:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[300686:0221/114711.039111:ERROR:cert_verify_proc_builtin.cc(690)] CertVerifyProcBuiltin for 127.0.0.1 failed:
----- Certificate i=0 (CN=LOCLAP385) -----
ERROR: No matching issuer found


No protocol specified
No protocol specified
No protocol specified
No protocol specified
[300716:0221/114711.790918:ERROR:vaapi_wrapper.cc(682)] Could not get a valid VA display
[300716:0221/114711.792887:ERROR:x11_software_bitmap_presenter.cc(141)] XGetWindowAttributes failed for window 41943043
[300716:0221/114711.793094:ERROR:x11_software_bitmap_presenter.cc(141)] XGetWindowAttributes failed for window 41943050
[300716:0221/114711.793430:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
^C[300717:0221/114808.521313:ERROR:ssl_client_socket_impl.cc(983)] handshake failed; returned -1, SSL error code 1, net_error -101

The output of the self-checker:

sthukral@LOCLAP385:/opt/intel/oneapi/vtune/latest/bin64$ sudo ./vtune-self-checker.sh 
Intel(R) VTune(TM) Profiler Self Check Utility
Copyright (C) 2009 Intel Corporation. All rights reserved.
Build Number: 624757

HW event-based analysis (counting mode) (Intel driver)   
Example of analysis types: Performance Snapshot
    Collection: Ok
    Finalization: Ok...
    Report: Ok

Instrumentation based analysis check   
Example of analysis types: Hotspots and Threading with user-mode sampling
    Collection: Ok
    Finalization: Ok...
    Report: Ok

HW event-based analysis check (Intel driver)   
Example of analysis types: Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
    Collection: Ok
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis check (Intel driver)   
Example of analysis types: Microarchitecture Exploration
    Collection: Ok
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis with uncore events (Intel driver)   
Example of analysis types: Memory Access
    Collection: Ok
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis with stacks (Perf)   
Example of analysis types: Hotspots with HW event-based sampling and call stacks
    Collection: Ok
vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location.
    Finalization: Ok...
vtune: Warning: Cannot read load addresses of sections from `/sys/module/hid-logitech-dj/sections'. This may affect the correctness of symbol resolution for `/lib/modules/5.14.0-1057-oem/kernel/drivers/hid/hid-logitech-dj.ko'. Make sure this directory exists and all files in this directory have read permissions.
vtune: Warning: Cannot read load addresses of sections from `/sys/module/intel-ish-ipc/sections'. This may affect the correctness of symbol resolution for `/lib/modules/5.14.0-1057-oem/kernel/drivers/hid/intel-ish-hid/intel-ish-ipc.ko'. Make sure this directory exists and all files in this directory have read permissions.

vtune: Warning: Cannot read load addresses of sections from `/sys/module/nvidia-uvm/sections'. This may affect the correctness of symbol resolution for `/lib/modules/5.14.0-1057-oem/updates/dkms/nvidia-uvm.ko'. Make sure this directory exists and all files in this directory have read permissions.
vtune: Warning: Cannot read load addresses of sections from `/sys/module/i2c-i801/sections'. This may affect the correctness of symbol resolution for `/lib/modules/5.14.0-1057-oem/kernel/drivers/i2c/busses/i2c-i801.ko'. Make sure this directory exists and all files in this directory have read permissions.

vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis with context switches (Intel driver)   
Example of analysis types: Threading with HW event-based sampling
    Collection: Ok
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

Checking DPC++ application as prerequisite for GPU analyses: Fail
Unable to run DPC++ application on GPU connected to this system. If you are using an Intel GPU and want to verify profiling support for DPC++ applications, check these requirements:
* Install Intel(R) GPU driver.
* Install Intel(R) Level Zero GPU runtime.
* Install Intel(R) oneAPI DPC++ Runtime and set the environment.

The system is ready to be used for performance analysis with Intel VTune Profiler.
Review warnings in the output above to find product limitations, if any.

The system is ready for the following analyses:
* Performance Snapshot
* Hotspots and Threading with user-mode sampling
* Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
* Microarchitecture Exploration
* Memory Access
* Hotspots with HW event-based sampling and call stacks
* Threading with HW event-based sampling

The following analyses have failed on the system:
* GPU Compute/Media Hotspots (characterization mode)
* GPU Compute/Media Hotspots (source analysis mode)

Log location: /tmp/vtune-tmp-root/self-checker-2023.02.21_11.42.16/log.txt

And drivers are properly installed:

sthukral@LOCLAP385:/opt/intel/oneapi/vtune/latest/sepdk/src$ sudo ./insmod-sep -q
pax driver is loaded and owned by group "vtune" with file permissions "660".
socperf3 driver is loaded and owned by group "vtune" with file permissions "660".
sep5 driver is loaded and owned by group "vtune" with file permissions "660".

socwatch driver is loaded and owned by group "vtune" with file permissions "660".

vtsspp driver is loaded and owned by group "vtune" with file permissions "660".

If I don't add sudo to ./vtune-gui the GUI loads but with sudo it doesn't load. I need sudo because all the drivers are enabled in sudo mode. 

 

0 Kudos
4 Replies
JyothisV_Intel
Moderator
1,010 Views

Hi,


Good day to you.


Thanks for posting in Intel Communities.


Sorry for the inconvenience caused. This seems to be a known issue and we have reported this to our internal team.


We will get back to you with an update soon.


Regards,

Jyothis V James



0 Kudos
JyothisV_Intel
Moderator
851 Views

Hi,

 

Good day to you.

 

Apologies for the delay in getting back to you.

 

Our internal team has informed us that it is not necessary to run Intel® VTune™ Profiler as a sudo user to get elevated profiling privileges. You can add your username to the "vtune" group to provide sufficient privileges to Intel® VTune™ Profiler. This can be done using the below command:

 

sudo usermod -a -G vtune <username>

 

Reboot the system to see if the user have been added to the group by running the below command:

 

id <username> | grep vtune

 

 

Running Intel® VTune™ Profiler GUI as a super user/root user is disabled as a security feature/policy.

 

As an alternative approach you can use the Intel® VTune™ Backend (Web Server Interface) by running the below command:

sudo <vtune-install-dir>/bin64/vtune-backend --allow-remote-ui
Eg.:

 

sudo /opt/intel/oneapi/vtune/latest/bin64/vtune-backend --allow-remote-access

 

A URL will be generated which can be opened in your browser. The first time you access this URL, you will be shown a warning regarding self-signed certificate since the website is loaded locally, kindly confirm and bypass this warning to access the Intel® VTune™ Backend (Web Server Interface).

 

Refer Intel® VTune™ Backend (Web Server Interface) Documentation: https://www.intel.com/content/www/us/en/develop/documentation/vtune-help/top/launch/web-server-ui.html

 

If this resolves your query, kindly mark this as a solution as it will help others with a similar query. Do get back to us if you have any query/suggestion while using Intel® products or services. 

 

Thanks and Regards,

Jyothis V James

 

0 Kudos
JyothisV_Intel
Moderator
809 Views

Hi,


Good day to you.


We have not received an update from you. Is your query answered? It not, do get back to us.


Thanks and Regards,

Jyothis V James


0 Kudos
JyothisV_Intel
Moderator
746 Views

Hi,


Good day to you.


We have not heard back from you. We assume that your issue is resolved.


Intel will no longer monitor this thread. If you have any queries or suggestions related to using Intel products or services, kindly post a new question.


Thanks and Regards,

Jyothis V James



0 Kudos
Reply