From: "Bly, Mike" <mbly@ciena.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] migration from 17.05 to 17.11, testpmd not able to bring up ports for virtio instance running inside a VM
Date: Tue, 10 Jul 2018 15:55:03 +0000 [thread overview]
Message-ID: <CY1PR04MB2057EE7D0C98916C9BF2F038CF5B0@CY1PR04MB2057.namprd04.prod.outlook.com> (raw)
Does anyone have some suggestions on where to start with this ?
When we run this using DPDK 17.05, the ports come up fine for our design and testpmd. However, with 17.11, the ports to not come up and I end up with undefined rx_pkt_burst/tx_pkt_burst functions as shown here:
(gdb) p rte_eth_devices[0]
$1 = {
rx_pkt_burst = 0x0,
tx_pkt_burst = 0x0,
tx_pkt_prepare = 0x0,
data = 0x7f46c31b7640,
dev_ops = 0xab0580 <virtio_eth_dev_ops>,
device = 0x7f46c40240e0,
intr_handle = 0x7f46c40241b8,
link_intr_cbs = {
tqh_first = 0x7f46c318a200,
tqh_last = 0x7f46c318a200
},
post_rx_burst_cbs = {0x0 <repeats 1024 times>},
pre_tx_burst_cbs = {0x0 <repeats 1024 times>},
state = RTE_ETH_DEV_ATTACHED,
security_ctx = 0x0
}
Here is the sequence for testpmd using 17.11:
root:/# dpdk-devbind -s
Network devices using DPDK-compatible driver
============================================
0000:00:06.0 'Virtio network device 1000' drv=uio_pci_generic unused=vfio-pci
0000:00:07.0 'Virtio network device 1000' drv=uio_pci_generic unused=vfio-pci
Network devices using kernel driver
===================================
0000:00:03.0 'Virtio network device 1000' if=eth0 drv=virtio-pci unused=vfio-pci,uio_pci_generic
Other Network devices
=====================
<none>
Crypto devices using DPDK-compatible driver
===========================================
<none>
Crypto devices using kernel driver
==================================
<none>
Other Crypto devices
====================
<none>
Eventdev devices using DPDK-compatible driver
=============================================
<none>
Eventdev devices using kernel driver
====================================
<none>
Other Eventdev devices
======================
<none>
Mempool devices using DPDK-compatible driver
============================================
<none>
Mempool devices using kernel driver
===================================
<none>
Other Mempool devices
=====================
<none>
root:/# testpmd -c 7 -n 3 -b 0000:00:03.0 -- -i --nb-cores=2 --nb-ports=2
EAL: Detected 4 lcore(s)
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL: Device is blacklisted, not initializing
EAL: PCI device 0000:00:06.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
EAL: PCI device 0000:00:07.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
Interactive-mode selected
USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=163456, size=2176, socket=0
Configuring Port 0 (socket 0)
EAL: Unknown handle type of fd 20
EAL: Unknown handle type of fd 20
Fail to start port 0
Configuring Port 1 (socket 0)
EAL: Unknown handle type of fd 22
EAL: Unknown handle type of fd 22
Fail to start port 1
Please stop the ports first
Done
testpmd>
Mike Bly | Principal Software Engineer/Architect, Packet Software & Access - Advanced Development
mbly@ciena.com<mailto:mbly@ciena.com> | 12730 E. Mirabeau Pkwy | Spokane Valley, WA 99216
Direct +1.509.242.9246 | Fax +1.509.242.9001
reply other threads:[~2018-07-10 15:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CY1PR04MB2057EE7D0C98916C9BF2F038CF5B0@CY1PR04MB2057.namprd04.prod.outlook.com \
--to=mbly@ciena.com \
--cc=dev@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).