Closed VogelIBR closed 1 year ago
you have to bind the network card to a DPDK driver first using the dpdk/usertools/dpdk-devbind.py script
Thanks for the reply.
Did I set it wrong?
$dpdk-devbind.py --status
Network devices using DPDK-compatible driver
============================================
0000:41:00.0 'MT27800 Family [ConnectX-5] 1017' drv=vfio-pci unused=mlx5_core
0000:41:00.1 'MT27800 Family [ConnectX-5] 1017' drv=vfio-pci unused=mlx5_core
Network devices using kernel driver
===================================
0000:01:00.0 'MT27800 Family [ConnectX-5] 1017' if=eno33np0 drv=mlx5_core unused=vfio-pci *Active*
0000:01:00.1 'MT27800 Family [ConnectX-5] 1017' if=eno34np1 drv=mlx5_core unused=vfio-pci
Still results in
EAL: Probe PCI driver: mlx5_pci (15b3:1017) device: 0000:41:00.0 (socket 0)
mlx5_common: No Verbs device matches PCI device 0000:41:00.0, are kernel drivers loaded?
mlx5_common: Verbs device not found: 0000:41:00.0
mlx5_common: Failed to initialize device context.
EAL: Requested device 0000:41:00.0 cannot be used
EAL: Bus (pci) probe failed.
TELEMETRY: No legacy callbacks, legacy socket not created
lib_init_hw@ 129 [CORE 0] !!!! Port 0 is not present on the board
EAL: Error - exiting with code: 1
Cause: check_port_config failed
T₄P₄S switch running ./examples/basic-mirror.p4 exited with error code 1
- Runtime options were: -a 0000:41:00.0 0000:41:00.1 -- -p 0x3 --config "\"(0,0,0)\""
Ok nvm, with mellanox mlx5_core
should be the right driver, even though it does not show up as dpdk-compatible in the dpdk-devbind.py --status
.
I actually got it working now with the mlx5_core
driver. I think it might just have been a typo in the config that causes the error.
Hi,
Are there configuration options which network card t4p4s should use? I want to use real network cards, e.g., eno34np1
I tried changing the network mask to, e.g.,
0x4
but t4p4s complains with the following error:Thanks