> Interestingly, I had already modified those 4 lines in dpdk.mk from 'n' to > 'y' and I still get the "EAL: Driver cannot attach the device" errors when > starting VPP.
Do you have LD_LIBRARY_PATH exported so that the DPDK can find the librte_pmd_mlx[45]_glue.so.* library? Eg. from the the vpp build path: ~# ls $PWD/build-root/install-vpp-native/external/lib/*glue* ./build-root/install-vpp-native/external/lib/librte_pmd_mlx4_glue.so.18.02.0 ./build-root/install-vpp-native/external/lib/librte_pmd_mlx5_glue.so.19.08.0 ~# export LD_LIBRARY_PATH=$PWD/build-root/install-vpp-native/external/lib This is necessary for the MLX DPDK PMD. > I noticed in your config file above that it says DPDK_VERSION ?= 19.08 Yes, I am using master - but VPP build will use the right DPDK version automatically, I do not expect different results. > Also, could you please share the dpdk section of your VPP startup.conf? Same here. > On another note, when you say that I should use static ARP as a > workaround, I assume you mean using VPP's 'set ip arp' command, right? Yes. > One other thing my colleague discovered that might affect the situation is > weirdness with the TAP interfaces on Azure (dtap0 and dtap1) Ha this is interesting, I'll test that, thanks. ben
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15303): https://lists.fd.io/g/vpp-dev/message/15303 Mute This Topic: https://lists.fd.io/mt/69987045/21656 Mute #vpp: https://lists.fd.io/mk?hashtag=vpp&subid=1480452 Mute #dpdk: https://lists.fd.io/mk?hashtag=dpdk&subid=1480452 Mute #azure: https://lists.fd.io/mk?hashtag=azure&subid=1480452 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
