segmentation fault on KVM

[Dimitry_N_Intel]

Hi , 

I using benchmark_app on Ubuntu 22.04 and getting segmentation fault.

[Step 1/11] Parsing and validating input arguments
[ INFO ] Parsing input parameters
[Step 2/11] Loading OpenVINO Runtime
[ INFO ] OpenVINO:
[ INFO ] Build ................................. 2023.1.0-12185-9e6b00e51cd-releases/2023/1
[ INFO ]
[ INFO ] Device info:
[ INFO ] CPU
[ INFO ] Build ................................. 2023.1.0-12185-9e6b00e51cd-releases/2023/1
[ INFO ]
[ INFO ]
[Step 3/11] Setting device configuration
[ WARNING ] Performance hint was not explicitly specified in command line. Device(CPU) performance hint will be set to THROUGHPUT.
[Step 4/11] Reading model files
[ INFO ] Loading model files
[ INFO ] Read model took 16.75 ms
[ INFO ] Original model I/O parameters:
[ INFO ] Network inputs:
[ INFO ] image (node: image) : f32 / [...] / [1,3,384,480]
[ INFO ] Network outputs:
[ INFO ] 206 (node: aten::mul/Multiply) : f32 / [...] / [1,1000,2]
[ INFO ] 203 (node: __module.dkd/aten::squeeze/Squeeze_332) : f32 / [...] / [1,1000]
[ INFO ] 201 (node: __module.dkd/aten::transpose/Transpose) : f32 / [...] / [1,1000,64]
[Step 5/11] Resizing model to match image sizes and given batch
[ WARNING ] image: layout is not set explicitly, so it is defaulted to NCHW. It is STRONGLY recommended to set layout manually to avoid further issues.
[Step 6/11] Configuring input of the model
[ INFO ] Model batch size: 1
[ INFO ] Network inputs:
[ INFO ] image (node: image) : u8 / [N,C,H,W] / [1,3,384,480]
[ INFO ] Network outputs:
[ INFO ] 206 (node: aten::mul/Multiply) : f32 / [...] / [1,1000,2]
[ INFO ] 203 (node: __module.dkd/aten::squeeze/Squeeze_332) : f32 / [...] / [1,1000]
[ INFO ] 201 (node: __module.dkd/aten::transpose/Transpose) : f32 / [...] / [1,1000,64]
[Step 7/11] Loading the model to the device
[ ERROR ] Exception from src/inference/src/core.cpp:114:
[ GENERAL_ERROR ] Reduce node with name 'aten::linalg_norm/ReduceL2' has not found jit_uni_reduce_post_kernel_f32.

lscpu

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 40 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 24
On-line CPU(s) list: 0-23
Vendor ID: GenuineIntel
Model name: Common KVM processor
CPU family: 15
Model: 6
Thread(s) per core: 1
Core(s) per socket: 12
Socket(s): 2
Stepping: 1
BogoMIPS: 4589.21
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht sy
scall nx lm constant_tsc nopl xtopology cpuid tsc_known_freq pni cx16 x2apic hypervisor lahf_lm cpuid_f
ault pti
Virtualization features:
Hypervisor vendor: KVM
Virtualization type: full
Caches (sum of all):
L1d: 768 KiB (24 instances)
L1i: 768 KiB (24 instances)
L2: 96 MiB (24 instances)
L3: 32 MiB (2 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-23
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: KVM: Mitigation: VMX unsupported
L1tf: Mitigation; PTE Inversion
Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
Meltdown: Mitigation; PTI
Mmio stale data: Unknown: No mitigations
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Vulnerable
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Srbds: Not affected
Tsx async abort: Not affected

No error when running on Alder Lake.

Is there HW system limitation ?

[Hairul_Intel]

Hi Dimitry_N_Intel,

Thank you for reaching out to us.

Based on the information you've provided, you're running OpenVINO Toolkit in a Virtual Machine (VM).

Furthermore, seems like you are using VM with maximum available ISA equals SSE2 (most likely default KVM behavior to support heterogeneity). Minimum supported ISA for OpenVINO CPU is SSE4.2.

The recommendation regarding this issue is to change your VM properties.

Regards,

Hairul

[Hairul_Intel]

Hi Dimitry_N_Intel,

This thread will no longer be monitored since we have provided suggestion. If you need any additional information from Intel, please submit a new question.

Regards,

Hairul