We have the problem of running the dpdk-l3fwd application inside a VM.

The tool can’t be started inside the VM with the following error message:

 

dpdk-l3fwd -l 1 -- -p 0x3 --config="(0,0,1),(1,0,1)"  --parse-ptype

 

EAL: Detected CPU lcores: 9

EAL: Detected NUMA nodes: 1

EAL: Detected static linkage of DPDK

EAL: Multi-process socket /var/run/dpdk/rte/mp_socket

EAL: Selected IOVA mode 'PA'

EAL: Probe PCI driver: net_virtio (1af4:1000) device: 0000:00:04.0 (socket -1)

EAL: Probe PCI driver: net_virtio (1af4:1000) device: 0000:00:05.0 (socket -1)

TELEMETRY: No legacy callbacks, legacy socket not created

soft parse-ptype is enabled

Neither ACL, LPM, EM, or FIB selected, defaulting to LPM

L3FWD: Missing 1 or more rule files, using default instead

Initializing port 0 ... Creating queues: nb_rxq=1 nb_txq=1... Port 0 modified RSS hash function based on hardware support,requested:0xa38c configured:0

Ethdev port_id=0 requested Rx offloads 0xe doesn't match Rx offloads capabilities 0x2201 in rte_eth_dev_configure()

EAL: Error - exiting with code: 1

  Cause: Cannot configure device: err=-22, port=0

 

Could you please advise on what have been done in configuration in wrong way?

Please find below the details of environment preparation.

 

Additional note: on the same VM with the same configuration testpmd is being run successfully and traffic is being offloaded without any issues.

 

Env details:

1. We use the VM image based on ‘RedHat 8.8’ with DPDK 22.11.2 LTS. We have built DPDK inside VM with the following command:

meson --buildtype=debug -Dexamples=all -Dplatform=generic x86_64-native-linuxapp-gcc

ninja -C x86_64-native-linuxapp-gcc

2. Additionally, we have configured 1G huge pages.
   

 

3. We have used the following command to start the VM:

 

taskset -c 3,5,7,9,15,17,19,21,23 /usr/libexec/qemu-kvm -enable-kvm \

-cpu host -m 8192 \

-object memory-backend-file,id=mem,size=8192M,mem-path=/mnt/huge,share=on \

-numa node,memdev=mem -mem-prealloc -smp 9 \

-chardev socket,id=char0,path=/usr/local/var/run/stdvio5,server=on \

-netdev type=vhost-user,id=mynet0,chardev=char0,vhostforce=on,queues=1 \

-device virtio-net-pci,packed=on,mq=on,vectors=4,rx_queue_size=1024,tx_queue_size=1024,netdev=mynet0,mac=52:54:00:00:0a:01,mrg_rxbuf=on \

-chardev socket,id=char1,path=/usr/local/var/run/stdvio6,server=on \

-netdev type=vhost-user,id=mynet1,chardev=char1,vhostforce=on,queues=1 \

-device virtio-net-pci,packed=on,mq=on,vectors=4,rx_queue_size=1024,tx_queue_size=1024,netdev=mynet1,mac=52:54:00:00:0a:02,mrg_rxbuf=on \

-net user,hostfwd=tcp::10021-:22 \

-net nic,macaddr=52:54:00:00:0a:01 \

-nographic /tmp/vm1.qcow2

 

 

4. Once VM is started the following configuration is inside the VM:

5. Host configuration:
1. 
   
   Red Hat Enterprise Linux 8.7 (Ootpa), Linux 4.18.0-425.19.2.el8_7.x86_64