From: <hfli@netitest.com>
To: <matan@mellanox.com>
Cc: <users@dpdk.org>, <azuredpdk@microsoft.com>
Subject: [dpdk-users] DPDK procedure start Error: "PMD: Could not add multiq qdisc (17): File exists"
Date: Fri, 4 Jan 2019 11:46:48 +0800 [thread overview]
Message-ID: <000f01d4a3e0$1f6bb060$5e431120$@netitest.com> (raw)
In-Reply-To:
Hi Matan,
Could you help us for below error?
PMD: Could not add multiq qdisc (17): File exists
PMD: dtap0: failed to create multiq qdisc.
PMD: Disabling rte flow support: File exists(17)
PMD: Remote feature requires flow support.
PMD: TAP Unable to initialize net_tap_net_vdev_netvsc0_id0
EAL: Driver cannot attach the device (net_tap_net_vdev_netvsc0_id0)
PMD: net_failsafe: sub_device 1 probe failed (No such file or directory)
PMD: net_failsafe: MAC address is 06:5f:a6:0a:b4:f9
vdev_probe(): failed to initialize : PMD: net_failsafe: MAC address is
06:5f:a6:0a:b4:f9
device
EAL: Bus (vdev) probe failed.
Our DPDK procedure want to deploy on Hyper-v and Azure Cloud, so we try it
on Hyper-v firstly. It need start 2 processes, a client process use port1, a
server process use port2, port1 and port2 in one internal subnet on a
virtual switch,
But only one process can be started successfully, the other said error,
"PMD: Could not add multiq qdisc (17): File exists", our procedure is
running well on Vmware/KVM/ASW, is there any help for this?
Below is our env:
OS: Windows 10 and Hyper-V on it
Guest OS: CentOS7.6(Upgrade kernel to 4.20.0)
DPDK version: 18.02.2
# uname -a
Linux localhost.localdomain 4.20.0-1.el7.elrepo.x86_64 #1 SMP Sun Dec 23
20:11:51 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
root:/# ifconfig -a
bond0: flags=5122<BROADCAST,MASTER,MULTICAST> mtu 1500
ether 46:28:ec:c8:7a:74 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 75 bytes 6284 (6.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 75 bytes 6284 (6.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
mgmt1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.16.130 netmask 255.255.255.0 broadcast 192.168.16.255
inet6 fe80::78e3:1af8:3333:ff45 prefixlen 64 scopeid 0x20<link>
ether 00:15:5d:10:85:14 txqueuelen 1000 (Ethernet)
RX packets 5494 bytes 706042 (689.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2163 bytes 438205 (427.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
mgmt2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:15:5d:10:85:15 txqueuelen 1000 (Ethernet)
RX packets 3131 bytes 518243 (506.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
port1: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500
ether 00:15:5d:10:85:16 txqueuelen 1000 (Ethernet)
RX packets 1707 bytes 163778 (159.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 693 bytes 70666 (69.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
port2: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500
ether 00:15:5d:10:85:17 txqueuelen 1000 (Ethernet)
RX packets 900 bytes 112256 (109.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1504 bytes 122428 (119.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root:/# ethtool -i port1
driver: hv_netvsc
version:
firmware-version: N/A
expansion-rom-version:
bus-info:
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
root:/# ethtool -i port2
driver: hv_netvsc
version:
firmware-version: N/A
expansion-rom-version:
bus-info:
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
root:/#
Start server process successfully
# ./VM_DPDK -l 3 -n 4 --vdev="net_vdev_netvsc1,iface=port2" --socket-mem
1500 --file-prefix server
EAL: Detected 4 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Multi-process socket /var/log/.server_unix
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
PMD: net_failsafe: Initializing Fail-safe PMD for
net_failsafe_net_vdev_netvsc1_id0
PMD: net_failsafe: Creating fail-safe device on NUMA socket 0
PMD: Initializing pmd_tap for net_tap_net_vdev_netvsc1_id0 as dtap0
PMD: net_failsafe: MAC address is 00:15:5d:10:85:17
Concorrently start client process failed
# ./VM_DPDK -l 2 -n 4 --vdev="net_vdev_netvsc0,iface=port1" --socket-mem
1500 --file-prefix client
EAL: Detected 4 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Multi-process socket /var/log/.client_unix
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
PMD: net_failsafe: Initializing Fail-safe PMD for
net_failsafe_net_vdev_netvsc0_id0
PMD: net_failsafe: Creating fail-safe device on NUMA socket 0
PMD: Initializing pmd_tap for net_tap_net_vdev_netvsc0_id0 as dtap0
PMD: Could not add multiq qdisc (17): File exists
PMD: dtap0: failed to create multiq qdisc.
PMD: Disabling rte flow support: File exists(17)
PMD: Remote feature requires flow support.
PMD: TAP Unable to initialize net_tap_net_vdev_netvsc0_id0
EAL: Driver cannot attach the device (net_tap_net_vdev_netvsc0_id0)
PMD: net_failsafe: sub_device 1 probe failed (No such file or directory)
PMD: net_failsafe: MAC address is 06:5f:a6:0a:b4:f9
vdev_probe(): failed to initialize : PMD: net_failsafe: MAC address is
06:5f:a6:0a:b4:f9
device
EAL: Bus (vdev) probe failed.
Thanks and Regards,
Jack
next reply other threads:[~2019-01-04 3:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 3:46 hfli [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-04 5:27 [dpdk-users] 答复: " hfli
2019-01-07 21:26 ` [dpdk-users] " Stephen Hemminger
2019-01-08 1:36 ` [dpdk-users] 答复: " hfli
2019-01-08 19:32 ` [dpdk-users] " Stephen Hemminger
2019-01-08 19:35 ` Stephen Hemminger
2019-01-09 0:38 ` [dpdk-users] 答复: " hfli
2019-01-09 19:55 ` [dpdk-users] " Stephen Hemminger
2018-12-30 12:18 hfli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000f01d4a3e0$1f6bb060$5e431120$@netitest.com' \
--to=hfli@netitest.com \
--cc=azuredpdk@microsoft.com \
--cc=matan@mellanox.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).