Thanks for your reply and for looping in Damjan. I have had a fair bit of success initializing DPDK directly on this same box on the same adapters. Both of the following testpmd commands work for me and the interfaces are attached to properly: sudo ./testpmd -l 0-3 -n 4 --vdev='net_failsafe0,dev(0002:00:02.0)' --vdev='net_failsafe1,dev(0003:00:02.0)' -b 0001:00:02.0 -- -i sudo ./testpmd -l 0-3 -n 4 --vdev='net_vdev_netvsc0,iface=eth1' --vdev='net_vdev_netvsc1,iface=eth2' -b 0001:00:02.0 -- -i
Now, my DPDK devices are configured like this in the VPP config: dev 0002:00:02.0 vdev net_vdev_netvsc0,iface=eth1 dev 0003:00:02.0 vdev net_vdev_netvsc1,iface=eth2 And when I try to start VPP I see the following EAL parameters and failure to attach to the devices: 2020/01/23 19:02:45:346 warn dpdk *EAL init args: -c 2 -n 4 --in-memory --vdev net_vdev_netvsc0,iface=eth1 --vdev net_vdev_netvsc1,iface=eth2* --file-prefix vpp -w 0002:00:02.0 -w 0003:00:02.0 --master-lcore 1 2020/01/23 19:02:45:570 warn dpdk unsupported rx offloads requested on port 0: jumbo-frame 2020/01/23 19:02:45:572 warn dpdk unsupported rx offloads requested on port 2: jumbo-frame 2020/01/23 19:02:45:574 notice dpdk EAL: Detected 4 lcore(s) 2020/01/23 19:02:45:574 notice dpdk EAL: Detected 1 NUMA nodes 2020/01/23 19:02:45:574 notice dpdk EAL: No available hugepages reported in hugepages-1048576kB 2020/01/23 19:02:45:574 notice dpdk EAL: No free hugepages reported in hugepages-1048576kB 2020/01/23 19:02:45:574 notice dpdk EAL: No available hugepages reported in hugepages-1048576kB 2020/01/23 19:02:45:574 notice dpdk EAL: Probing VFIO support... 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xa80001000 != 0x7f0ac0000000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xc00002000 != 0x7f0280000000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xd80003000 != 0x7efa40000000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc0a64000 != 0x7ef63fe00000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc16c5000 != 0x7ef23fc00000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc2326000 != 0x7eee3fa00000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc2f87000 != 0x7eea3f800000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles ! 2020/01/23 19:02:45:574 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3) 2020/01/23 19:02:45:574 notice dpdk *EAL: Driver cannot attach the device (0002:00:02.0)* 2020/01/23 19:02:45:574 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 19:02:45:574 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:45:574 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth2" (index 4) 2020/01/23 19:02:45:574 notice dpdk *EAL: Driver cannot attach the device (0003:00:02.0)* 2020/01/23 19:02:45:574 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 19:02:45:574 notice dpdk net_failsafe: sub_device 0 probe failed (File exists) 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:45:574 notice dpdk EAL: VFIO support not initialized 2020/01/23 19:02:45:574 notice dpdk EAL: Couldn't map new region for DMA 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:47:533 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 19:02:47:533 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 19:02:47:533 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) Is there something I can do in the VPP startup.conf to get DPDK devices to initialize correctly? Thanks!
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15239): https://lists.fd.io/g/vpp-dev/message/15239 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] -=-=-=-=-=-=-=-=-=-=-=-
