Hi Alipour, It looks suspicious that on the host you don't see logs about loaded drivers, like these ones that you see inside the VM:
> 2024-12-03 19:32:36.642042 EAL: open shared lib > /usr/lib/dpdk/pmds-24.0/librte_net_fm10k.so.24.0 > 2024-12-03 19:32:36.642266 EAL: pmd.net.fm10k.init log level changed from > disabled to notice > 2024-12-03 19:32:36.642279 EAL: pmd.net.fm10k.driver log level changed from > disabled to notice > 2024-12-03 19:32:36.642285 EAL: open shared lib > /usr/lib/dpdk/pmds-24.0/librte_net_qdma.so.24.0 > 2024-12-03 19:32:36.642581 EAL: open shared lib > /usr/lib/dpdk/pmds-24.0/librte_net_vhost.so > 2024-12-03 19:32:36.643201 EAL: lib.dmadev log level changed from disabled > to info > 2024-12-03 19:32:36.643264 EAL: Registered [vdpa] device class. Can it be that DPDK on the host does not see shared libraries, e.g. it is not installed in the system and LD_LIBRARY_PATH is not set to shared library location? Then mempool driver would just not be loaded to create a mempool.
