Closed ader1990 closed 5 years ago
You shall run dpdk-iperf3 -c 10.0.0.2 on another VM with another ANS. By the way the IP 10.0.0.2 shall be changed on the client side.
no feadback. close it.
You shall run dpdk-iperf3 -c 10.0.0.2 on another VM with another ANS. By the way the IP 10.0.0.2 shall be changed on the client side.
I have deployed two vms on Azure. Each VM has one management nic and one data nic. The data nic on each vm is in the same Azure subnet (the data nics are both connected to the same switch). I started on each VM an ANS environment and on one VM started the dpdk_iperf 3 server and on the other VM started the iperf3 client. The iperf3 client failed (error message bellow):
root@sender:~/dpdk-iperf# ./dpdk_iperf3 -c 10.1.0.2
EAL: Detected 16 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_28520_ad41f49827a
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
USER8: LCORE[-1] anssock any lcore id 0xffffffff
USER8: LCORE[2] anssock app id: 28520
USER8: LCORE[2] anssock app name: dpdk_iperf3
USER8: LCORE[2] anssock app lcoreId: 2
USER8: LCORE[2] mp ops number 4, mp ops index: 0
fcntl(F_GETFL): Bad file descriptor
Please note that in the same setup I could make testpmd and Openvswitch with DPDK work.
Please ignore this error message "fcntl(F_GETFL): Bad file descriptor". Please share ans startup log on client and server side. Please share dpdk-iperf3 startup log on client and server side.
I am using DPDK 18.11 with Linux kernel 4.20.7 on an Azure VM, where I have Mellanox SRIOV nics (accelerated network).
I start the ANS env (looks fine):
Then I start DPDK Iperf3 server (looks fine):
Then I start the DPDK Iperf3 client, which fails:
Does someone know what I am doing wrong? Thanks.