We are using IPSec-mb library version 1.2.0 with dpdk for crypto acceleration. On vmware we are seeing a crash below when it tries to execute avx512 instruction. The mb_mgr shows that the AVX512 is detected by library.(see features below). But the vmware proc/cpuinfo does not show the avx512 instruction set as supported. We saw that X86_FEATURE_XSAVE is not enabled in the VM and avx512 instruction depends on this instruction (from https://github.com/torvalds/linux/blob/master/arch/x86/kernel/cpu/cpuid-deps.c). So our suspect is that the ipsecMB library is not considering this XSAVE before detecting AVX/AVX512 feature. Can you please let us know if this is correct and is there any fix for this issue?

#0 0x00007f4983153cf6 in init_mb_mgr_avx512 () from /lib/x86_64-linux-gnu/libIPSec_MB.so.1
(gdb) bt
#0 0x00007f4983153cf6 in init_mb_mgr_avx512 () from /lib/x86_64-linux-gnu/libIPSec_MB.so.1
#1 0x00007f49831c39f5 in init_mb_mgr_auto () from /lib/x86_64-linux-gnu/libIPSec_MB.so.1
#2 0x0000558fafe584aa in ipsec_mb_alloc_mgr_from_memzone (mb_mgr_mz_name=0x7ffe83246860 "IMB_MGR_DEV_0_QP_0", mb_mgr_mz=0x10c1b20d0) at ../drivers/crypto/ipsec_mb/ipsec_mb_ops.c:189
#3 ipsec_mb_qp_setup (dev=0x558fbbf15480 <rte_crypto_devices>, qp_id=, qp_conf=0x7ffe83246930, socket_id=0) at ../drivers/crypto/ipsec_mb/ipsec_mb_ops.c:248

(gdb) p *mb_mgr
$6 = {
flags = 0,
features = 315390,