topic Re: VTune cannot detect local machine configuration in Analyzers

VTune cannot detect local machine configuration

Daniel_D — Sun, 25 Aug 2024 07:42:06 GMT

Hi,

unfortunately I run into issues starting vtune. I use the latest oneAPI (20242.2.1)

No matter if I run vtune from vs2022 or from command line I do get this error. running on windows 11 with all updates.

Any idea what I'm doing wrong here?

Here some additional information:
C:\Windows\System32>"C:\Program Files (x86)\Intel\oneAPI\vtune\2024.2\bin64\sep" -version
Sampling Enabling Product Version: 5.48 Beta built on Jul 29 2024 12:31:32
SEP Driver Version: 5.48 Beta (public)
PAX Driver Version: 1.0
Platform type: 122
CPU name: Intel(R) microarchitecture code named Coffeelake
PMU: skylake
Driver configs: Maskable Interrupt, OFFCORE OFF (by OS security), REGISTER CHECK ON
Virtualization platform: Host VM on Hyper-V with VBS enabled
Copyright(C) 2007 Intel Corporation. All rights reserved.

Just noticed: advisor didn't start at all from VS2022 (EXTENSIONS->Intel->Analyze performance with Intel Advisor).

Thanks.

Re: VTune cannot detect local machine configuration

yuzhang3_intel — Mon, 26 Aug 2024 01:30:51 GMT

Please run the self-check utility and post the log.

C:\Windows\System32>"C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune-self-checker.bat"

Run the command line below and share the output with me; thanks.

C:\Windows\System32>"C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\amplxe-runss.exe" --context-value-list

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 01:42:36 GMT

Hi,

selfchecker with command gives this:

C:\Windows\System32>>"C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune-self-checker.bat"
The syntax of the command is incorrect.

I then run it with powershell. the log is attached.

The second one did not make any output I could see:

PS C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64> ./amplxe-runss --context-value-list
PS C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64>

Let me know if you need more information.

Daniel

Re: VTune cannot detect local machine configuration

yuzhang3_intel — Mon, 26 Aug 2024 02:00:01 GMT

Please run amplxe-sepreg.exe -u / -i uninstall / install the VTune driver again. It looks like the driver is not available from the log.

C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64>amplxe-sepreg.exe -h

Usage: amplxe-sepreg.exe [ option ]

where option is one of the following:

-c | --check-dependencies
-i | --install-driver
-s | --status
-u [pax]| --uninstall-driver [pax]

-v | --verbose may also be added to the above option for additional output

Check driver:
isSEPDriverAvailable: False
isPAXDriverLoaded: False
The SEP driver is not available.
================================================================================
SEP version:
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\2024.2\bin64\sep.exe -version
Stdout:
  Sampling Enabling Product Version: 5.48 Beta built on Jul 29 2024 12:31:32
  SEP Driver Version: PAX Driver Version: Platform type: 122
  CPU name: Intel(R) microarchitecture code named Coffeelake
  PMU: skylake
Stderr:
  Error retrieving SEP driver version
  Error retrieving PAX driver version

Check driver with sep -version: Fail

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 02:06:38 GMT

OK- I run it as admin and get now this output for -c

PS C:\WINDOWS\system32> cd "\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64"
PS C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64> ./amplxe-sepreg.exe -c
Checking platform...
Platform is genuine Intel: OK
Platform has SSE2: OK
Platform architecture: INTEL64
User has admin rights: OK
Drivers will be installed to C:\WINDOWS\System32\Drivers\
Checking sepdrv5 driver path...OK
Checking sepdrv5 service...
Driver status: the sepdrv5 service is running
Checking sepdal driver path...OK
Checking sepdal service...
Driver status: the sepdal service is running
Checking socperf3 driver path...OK
Checking socperf3 service...
Driver status: the socperf3 service is running
Checking vtss driver path...OK
Checking vtss service...FAILED
PS C:\Program Files (x86)\Intel\o

./amplxe-runss.exe --context-value-list still without output i can see
PS C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64> ./amplxe-runss.exe --context-value-list
PS C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64>

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 02:22:46 GMT

Do I need any exceptions in the windows defender?

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 02:50:53 GMT

// bug-report was unrelated

Re: VTune cannot detect local machine configuration

yuzhang3_intel — Mon, 26 Aug 2024 03:26:04 GMT

Run amplxe-sepreg.exe -i to install the VTune driver again, and then run amplxe-sepreg.exe -s to double-check if the driver is ready.

Following the steps for Windows defender setting.

HW SAMPLING COLLECTION CONFLICT DUE TO WINDOWS DEFENDER VIRUS PROTECTION (DOC-10966)
The hardware sampling based collections (hotspots, uarch exploration, memory access, etc.) won't work correctly if Windows Defender Virus Protection is enabled as it is using the PMU counters for virus detection. In order to load the drivers, the user should also disable Windows Defender.

Steps to disable Windows Defender Real-time Virus Protection:

Search for "Windows Security" and click to open the app.
Click on "Virus & threat protection".
Under the section, click the "Manage settings" option.
Turn off the "Real-time protection" toggle switch to disable Microsoft Defender Antivirus.

Due to the security risk, users should disable Windows Defender at their own discretion.

Strange why there is no output from the command line below:

./amplxe-runss.exe --context-value-list

Run 'set' in the Windows command console and get the output.

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 03:34:14 GMT

C:\Windows\System32>cd "\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64"

C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64>amplxe-sepreg.exe -i
Warning, socperf3 driver is already installed and will be re-used... skipping
Installing and starting sepdrv5...
OK
Installing and starting sepdal...
OK
Installing and starting vtss...
OK

C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64>amplxe-sepreg.exe -s
Checking sepdrv5 driver path...OK
Checking sepdrv5 service...
Driver status: the sepdrv5 service is running
Checking sepdal driver path...OK
Checking sepdal service...
Driver status: the sepdal service is running
Checking socperf3 driver path...OK
Checking socperf3 service...
Driver status: the socperf3 service is running
Checking vtss driver path...OK
Checking vtss service...OK

C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64>

set gives:

ADVISOR_2024_DIR=C:\Program Files (x86)\Intel\oneAPI\advisor\2024.2
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Test\AppData\Roaming
BOOST_ROOT=W:\3rdParty\boost_1_85_0
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=DANIEL-DESKTOP
ComSpec=C:\WINDOWS\system32\cmd.exe
CUDA_PATH=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.4
CUDA_PATH_V10_2=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.2
CUDA_PATH_V11_2=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2
CUDA_PATH_V11_8=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.8
CUDA_PATH_V12_1=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1
CUDA_PATH_V12_2=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.2
CUDA_PATH_V12_3=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.3
CUDA_PATH_V12_4=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.4
CUDA_PATH_V9_0=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0
DriverData=C:\Windows\System32\Drivers\DriverData
DXSDK_DIR=C:\Program Files (x86)\Microsoft DirectX SDK (June 2010)\
GPA_MONITOR_MEMORY_NAME={4DB91066-DA48-4467-AC24-8002BD3D4E0B}6
GPU_MAX_ALLOC_PERCENT=100
GPU_MAX_HEAP_SIZE=100
GPU_MAX_SINGLE_ALLOC_PERCENT=100
GPU_MAX_USE_SYNC_OBJECTS=1
GPU_SINGLE_ALLOC_PERCENT=100
HOMEDRIVE=C:
HOMEPATH=\Users\Test
LIB=C:\Program Files (x86)\Intel\oneAPI\compiler\latest\lib
LOCALAPPDATA=C:\Users\Test\AppData\Local
LOGONSERVER=\\DANIEL-DESKTOP
MONITOR_ADDRESS=localhost:12721
NUMBER_OF_PROCESSORS=16
OneDrive=C:\Users\Test\OneDrive
OS=Windows_NT
path=C:\Program Files (x86)\Common Files\Oracle\Java\java8path;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\Llvm-18.1.8\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.4\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.4\libnvvp;C:\Python311\Scripts\;C:\Python311\;C:\Program Files (x86)\Intel\oneAPI\compiler\latest\windows\bin-llvm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Strawberry\c\bin;C:\Strawberry\perl\site\bin;C:\Strawberry\perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\ProgramData\chocolatey\bin;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\NVIDIA Corporation\Nsight Compute 2024.1.1\;C:\Program Files\Git\cmd;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files (x86)\Intel\oneAPI\compiler\latest\bin;C:\Program Files\NASM;C:\Program Files\PowerShell\7\;C:\Program Files\dotnet\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Intel\oneAPI\tbb\latest\redist\intel64\vc_mt\;C:\Users\Test\.dotnet\tools
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW
POWERSHELL_DISTRIBUTION_CHANNEL=MSI:Windows 10 Pro
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 158 Stepping 12, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=9e0c
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
PUBLIC=C:\Users\Public
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=R:\Temp
TMP=R:\Temp
TT_BOOST_ROOT=W:\3rdParty\boost_1_85_0
TT_BOOST_TOOLSET=vc143
TT_BOOST_VERSION=1_85
TT_CUDA_ROOT=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.4
TT_ONEAPI_ROOT=C:\Program Files (x86)\Intel\oneAPI
TT_OPENSSL_ROOT=W:\3rdParty\openssl
TT_RAPID_JSON_ROOT=W:\3rdParty\rapidjson
USERDOMAIN=DANIEL-DESKTOP
USERDOMAIN_ROAMINGPROFILE=DANIEL-DESKTOP
USERNAME=Test
USERPROFILE=C:\Users\Test
VTUNE_PROFILER_2024_DIR=C:\Program Files (x86)\Intel\oneAPI\vtune\2024.2
windir=C:\WINDOWS
ZES_ENABLE_SYSMAN=1

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 07:03:56 GMT

Hi. Any chance to get vtune working?

Re: VTune cannot detect local machine configuration

yuzhang3_intel — Mon, 26 Aug 2024 08:17:55 GMT

Is there output from 'emon.exe -v' ?

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 08:19:38 GMT

yes - please see below:

C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64>emon.exe -v
EMON Version .............. V11.48 Beta
Copyright(C) 1993 Intel Corporation. All rights reserved.
Application Build Date: Jul 29 2024 at 12:31:30
SEP Driver Version: 5.48 Beta (public)
PAX Driver Version: 1.0
Virtualization platform: Host VM on Hyper-V with VBS enabled
total_number_of_processors ...... 16
number_of_online_processors ...... 16
cpu_family ................ Intel(R) microarchitecture code named Coffeelake
cpu_model ................. 158 (0x9e)
cpu_stepping .............. 12 (0xc)

Cache Info (core):
L1 Data Cache ............. 32KB, 8-way, 64-byte line size
16 HW threads share this cache, No SW Init Required
L1 Code Cache ............. 32KB, 8-way, 64-byte line size
16 HW threads share this cache, No SW Init Required
L2 Unified Cache .......... 256KB, 4-way, 64-byte line size
16 HW threads share this cache, No SW Init Required
L3 Unified Cache .......... 16MB, 16-way, 64-byte line size
No SW Init Required
Data TLB .................. 4-way, 4K Pages, 64 entries
64-byte Prefetching

Device Type ............... Intel(R) microarchitecture code named Coffeelake
EMON Database ............. skylake
Platform type ............. 122

System Features:
(Number of Packages: 1)
(Cores Per Package:
(Threads Per Package: 16)

Processor Features (core):
number_of_selectors ....... 4
number_of_var_counters .... 4
number_of_fixed_ctrs....... 3
Fixed Counter Events:
counter 0 ................. INST_RETIRED.ANY
counter 1 ................. CPU_CLK_UNHALTED.THREAD
counter 2 ................. CPU_CLK_UNHALTED.REF_TSC
number of devices ......... 1
number_of_events .......... 617
(Thermal Throttling) (Enabled)
(Hyper-Threading) (Enabled)
(DCU IP Prefetching) (Enabled)
(DCU Streamer Prefetching) (Enabled)
(MLC Spatial Prefetching) (Enabled)
(MLC Streamer Prefetching) (Enabled)
(Threads Per Core: 2)

Uncore Performance Monitoring Units:
cbo : 8
imc : 1
edram : 1
ncu : 1
gt : 1

GPU Information:
No GPU devices found

RAM Features:
(Package/Memory Controller/Channel)
(0/0/0) (Total Number of Ranks on this Channel: 1)
(Dimm0 Info: Capacity = 16 GB, Data Width = 64, Form Factor = DIMM, Memory Type = DDR4, Memory Type Detail = Synchronous, Speed = 2933MHz, Configured Speed = 2933MHz)
(0/0/1) (Total Number of Ranks on this Channel: 1)
(Dimm0 Info: Capacity = 16 GB, Data Width = 64, Form Factor = DIMM, Memory Type = DDR4, Memory Type Detail = Synchronous, Speed = 2933MHz, Configured Speed = 2933MHz)

TSC Freq .................. 3600.00 MHz

NUMA node(s): 0

OS Processor <-> Physical/Logical Mapping
-----------------------------------------
OS Processor Phys. Package Core Logical Processor Core Type
0 0 0 0 core
1 0 0 1 core
2 0 1 0 core
3 0 1 1 core
4 0 2 0 core
5 0 2 1 core
6 0 3 0 core
7 0 3 1 core
8 0 4 0 core
9 0 4 1 core
10 0 5 0 core
11 0 5 1 core
12 0 6 0 core
13 0 6 1 core
14 0 7 0 core
15 0 7 1 core
-----------------------------------------

C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64>

Re: VTune cannot detect local machine configuration

yuzhang3_intel — Mon, 26 Aug 2024 08:27:41 GMT

The output from 'amplxe-runss.exe --context-value-list" is not observed (open console window as administrator), right?

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 08:47:44 GMT

take 2-3 seconds - but no output:

C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64>amplxe-runss.exe --context-value-list

C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64>

Re: VTune cannot detect local machine configuration

yuzhang3_intel — Mon, 26 Aug 2024 09:24:18 GMT

If you select the 'hotspots' analysis type with sw sampling mode, the issue is observed?

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 09:30:25 GMT

Not able to select any type of analysis - seems to required host config check first:

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 11:53:47 GMT

Can I try something else to get vtune working? Start from commandline gives the same error message:

VTune cannot detect local machine configuration.

Re: VTune cannot detect local machine configuration

yuzhang3_intel — Mon, 26 Aug 2024 12:49:12 GMT

From the current analysis, it looks like something is wrong with the environment setup that impacts VTune usage. Did VTune work on the same machine before the 2024.2.1 release?

By the way, can you share the Windows OS version and build number here?

Re: VTune cannot detect local machine configuration

Daniel_D — Mon, 26 Aug 2024 13:19:56 GMT

Hi,

yes, it worked in the past. Advisor worker never.

Re: VTune cannot detect local machine configuration

yuzhang3_intel — Mon, 26 Aug 2024 23:49:01 GMT

From the result of the self-check utility below, an extreme case when even the basic context-value-list could not be retrieved, and I am not aware of what could potentially cause this.

Context values:
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\2024.2\bin64\amplxe-runss.exe --context-value-list

Getting context values: Fail

Could you please collect detailed logs for amplxe-runss –context-value-list by launching it with PERFRUN_DEBUG=1 environment variable? It would produce the log in the current directory.

set PERFRUN_DEBUG=1

amplxe-runss –context-value-list