I’m far away from being dpdk-expert, I’m much closer to being expert in avoiding use of dpdk :)
No idea what’s wrong here, never used this failsafe beast, maybe using native rdma driver can help.... -- Damjan On 23 Jan 2020, at 18:13, Balaji Venkatraman via Lists.Fd.Io <balajiv=cisco....@lists.fd.io> wrote: cc-Damjan who is the DPDK expert. Not very conversant with failsafeEth. Looks like the driver isn’t able to connect to the device 2020/01/23 14:37:40:578 notice dpdk EAL: Driver cannot attach the device (0003:00:02.0) Here is some info I looked up regarding initializing the DPDK for Failsafe https://dpdk.readthedocs.io/en/v17.08/nics/fail_safe.html#using-the-fail-safe-pmd-from-the-eal-command-line HTH. -- Regards, Balaji. From: <vpp-dev@lists.fd.io> on behalf of Chris King <chriskin...@gmail.com> Date: Thursday, January 23, 2020 at 7:28 AM To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure Update: I had forgotten to modprobe (i.e. load) the ib_uverbs and mlx4_ib drivers which are required for my NICs on Azure. I noticed that something was wrong when looking at the output of 'sudo vppctl show log'. I then went back and tried to get DPDK's testpmd application to work and from the output there it pointed to the missing drivers. I did manage to get testpmd to attach to my drivers. However, things are still not working correctly from the VPP side (maybe it's the way that VPP is initializing DPDK?). Getting back to your question, I'm not sure what you mean by the remote end of the FailsafeEthernet0 interface since this is a DPDK interface using the failsafe PMD (netvsc, in this case). The underlying hardware this device is related to are the eth1 and rename6 interfaces since they have the same MAC address and the PCI address of 0002:00:02.0: sudo lshw -class network -businfo Bus info Device Class Description ==================================================== pci@0001:00:02.0 rename5 network MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] pci@0002:00:02.0 rename6 network MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] pci@0003:00:02.0 rename7 network MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] sudo ./dpdk-devbind.py --status Network devices using DPDK-compatible driver ============================================ <none> Network devices using kernel driver =================================== 0001:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename5 drv=mlx4_core unused= 0002:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename6 drv=mlx4_core unused= 0003:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename7 drv=mlx4_core unused= Now, if I try to bring up the interface on the link I get the following output in 'sudo vppctl show hardware': vpp# show hardware Name Idx Link Hardware FailsafeEthernet0 1 up FailsafeEthernet0 Link speed: 10 Gbps Ethernet address 00:0d:3a:f4:eb:8d FailsafeEthernet carrier up full duplex mtu 1504 flags: admin-up pmd maybe-multiseg rx-ip4-cksum rx: queues 1 (max 16), desc 1024 (min 0 max 65535 align 1) tx: queues 1 (max 16), desc 1024 (min 0 max 65535 align 1) max rx packet len: 1522 promiscuous: unicast off all-multicast off vlan offload: strip off filter off qinq off rx offload avail: ipv4-cksum udp-cksum tcp-cksum scatter rx offload active: ipv4-cksum scatter tx offload avail: ipv4-cksum udp-cksum tcp-cksum tcp-tso multi-segs tx offload active: multi-segs rss avail: ipv4-frag ipv4-tcp ipv4-udp ipv4-other ipv4 ipv6-tcp-ex ipv6-udp-ex ipv6-frag ipv6-tcp ipv6-udp ipv6-other ipv6-ex ipv6 rss active: none tx burst function: failsafe_tx_burst rx burst function: failsafe_rx_burst Errors: rte_eth_dev_start[port:0, errno:-19]: Unknown error -19 So, it's showing as up with with an error on the call to rte_eth_dev_start. Now 'sudo vppctl show log' shows these log entries (and the attach device entries keep repeating): 2020/01/23 14:37:40:578 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3) 2020/01/23 14:37:40:578 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 14:37:40:578 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:37:40:578 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) 2020/01/23 14:37:40:578 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 14:37:40:578 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth2" (index 4) 2020/01/23 14:37:40:578 notice dpdk EAL: Driver cannot attach the device (0003:00:02.0) 2020/01/23 14:37:40:578 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:37:40:578 notice dpdk net_failsafe: sub_device 0 probe failed (File exists) 2020/01/23 14:37:40:578 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 14:37:40:578 notice dpdk EAL: VFIO support not initialized 2020/01/23 14:37:40:578 notice dpdk EAL: Couldn't map new region for DMA 2020/01/23 14:37:40:578 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 14:37:40:578 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 14:37:42:510 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 14:37:42:510 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:33:24:210 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 14:33:24:210 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:33:24:210 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) 2020/01/23 14:33:24:210 notice dpdk EAL: Driver cannot attach the device (0003:00:02.0) 2020/01/23 14:33:24:210 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:33:24:210 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) 2020/01/23 14:33:26:215 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 14:33:26:215 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:33:26:215 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) 2020/01/23 14:33:26:215 notice dpdk EAL: Driver cannot attach the device (0003:00:02.0) But trying multiple times I usually still end up with carrier down and similar vppctl log entries, so I haven't got it working yet. Any pointers?
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15238): https://lists.fd.io/g/vpp-dev/message/15238 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] -=-=-=-=-=-=-=-=-=-=-=-
