All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: olivier.matz@6wind.com, pascal.mazon@6wind.com,
	shahafs@mellanox.com, maxime.coquelin@redhat.com, dev@dpdk.org
Subject: Fedora 28 fails DPDK 18.11 on Azure/Hyper-V
Date: Mon, 26 Nov 2018 13:30:46 -0800	[thread overview]
Message-ID: <20181126133046.4b118fc6@xeon-e3> (raw)

Started testing DPDK support of Hyper-V in Fedora and discovered that it doesn't work.
Looks like the multiq qdisc is not in the default Fedora kernel configuration.
Hopefully CentOS/RHEL don't have the same problem.

Not sure why SCH_MULTIQ is in the shipped kernel config files but not present.
Looks like a Fedora build or packaging issue.

# grep MULTIQ /boot/config*
/boot/config-4.18.13-200.fc28.x86_64:CONFIG_NET_SCH_MULTIQ=m
/boot/config-4.18.18-200.fc28.x86_64:CONFIG_NET_SCH_MULTIQ=m
/boot/config-4.19.2-200.fc28.x86_64:CONFIG_NET_SCH_MULTIQ=m

# modinfo sch_multiq
modinfo: ERROR: Module sch_multiq not found.


Testpmd log is:
# dpdk-testpmd --log-level 8 --log-level 'pmd.net.failsafe:debug' -l 1,2 -n 4 -- -i
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
EAL: PCI device a1e0:00:02.0 on NUMA socket 0
EAL:   probe driver: 15b3:1014 net_mlx5
net_mlx5: MPLS over GRE/UDP tunnel offloading disabled due to old OFED/rdma-core version or firmware configuration
net_failsafe: Initializing Fail-safe PMD for net_failsafe_vsc0
net_failsafe: Creating fail-safe device on NUMA socket 0
net_failsafe: a1e0:00:02.0
net_failsafe: net_tap_vsc0,remote=eth1
net_failsafe: Failsafe port 1 owner info: Fail-safe_0000000000000001
net_failsafe: Taking control of a probed sub device 0 named a1e0:00:02.0
rte_pmd_tap_probe(): Initializing pmd_tap for net_tap_vsc0 as dtap0
qdisc_create_multiq(): Could not add multiq qdisc (2): No such file or directory
eth_dev_tap_create(): dtap0: failed to create multiq qdisc.
eth_dev_tap_create():  Disabling rte flow support: No such file or directory(2)
eth_dev_tap_create(): Remote feature requires flow support.
eth_dev_tap_create(): TAP Unable to initialize net_tap_vsc0
EAL: Driver cannot attach the device (net_tap_vsc0)
EAL: Failed to attach device on primary process

             reply	other threads:[~2018-11-26 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 21:30 Stephen Hemminger [this message]
2018-11-26 21:38 ` Fedora 28 fails DPDK 18.11 on Azure/Hyper-V Maxime Coquelin
2018-11-26 21:47 ` Timothy Redaelli
2018-11-26 23:55   ` Stephen Hemminger

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=20181126133046.4b118fc6@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=olivier.matz@6wind.com \
    --cc=pascal.mazon@6wind.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.