Skip to content

error running "epwget" example app, got error "No Ethernet port!" #317

@terapackets

Description

@terapackets

Dear experts,

mTCP is very promising and i really want to try it for an application I am developing. However I failed to run the example (epget, epserver) with the error No Ethernet port!.

I started by following the instruction in readme of this repo:

./setup_mtcp_dpdk_env.sh /home/xyz/pkgs/mtcp/dpdk

Ran options 15, 18, 22

I ran option 24 twice to register my 2 10G ports (Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01))

Enter PCI address of device to bind to IGB UIO driver: 0000:01:00.0
Enter PCI address of device to bind to IGB UIO driver: 0000:01:00.1

The binding of the two ports looks ok

 ./dpdk/usertools/dpdk-devbind.py -s

Network devices using DPDK-compatible driver
============================================
0000:01:00.0 'Ethernet Controller 10-Gigabit X540-AT2 1528' drv=igb_uio unused=ixgbe
0000:01:00.1 'Ethernet Controller 10-Gigabit X540-AT2 1528' drv=igb_uio unused=ixgbe

Then in two separate terminals (both as root), I try to run epwget and epserver in the "apps/example" directory.
In the configure files for client server, I just made sure they are using "dpdk0" and "dpdk1" (which are in the output of ifconfig -a).
on the server side

# ./epserver -p . -f epserver.conf -N 2
Configuration updated by mtcp_setconf().
---------------------------------------------------------------------------------
Loading mtcp configuration from : epserver.conf
Loading interface setting
EAL: Detected 6 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Auto-detected process type: PRIMARY
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
path=/sys/kernel/mm/hugepages/hugepages-1048576kB/free_hugepages|
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: PCI device 0000:01:00.1 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 8086:1528 net_ixgbe
EAL: Auto-detected process type: PRIMARY
Configurations:
Number of CPU cores available: 2
Number of CPU cores to use: 2
Maximum number of concurrency per core: 10000
Maximum number of preallocated buffers per core: 10000
Receive buffer size: 8192
Send buffer size: 8192
TCP timeout seconds: 30
TCP timewait seconds: 0
NICs to print statistics:
---------------------------------------------------------------------------------
Interfaces:
Number of NIC queues: 2
---------------------------------------------------------------------------------
Loading routing configurations from : config/route.conf
fopen: No such file or directory
Skip loading static routing table
Routes:
(blank)
---------------------------------------------------------------------------------
Loading ARP table from : config/arp.conf
fopen: No such file or directory
Skip loading static ARP table
ARP Table:
(blank)
---------------------------------------------------------------------------------

Checking link statusdone
CPU 0: initialization finished.
[mtcp_create_context:1359] CPU 0 is now the master thread.
CPU 1: initialization finished.

On the client side, I got the error when running

# ./epwget /test 1 -f epwget.conf -N 2
Configuration updated by mtcp_setconf().
Application configuration:
URL: /test
# of total_flows: 1
# of cores: 1
Concurrency: 0
---------------------------------------------------------------------------------
Loading mtcp configuration from : epwget.conf
Loading interface setting
EAL: Detected 6 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Auto-detected process type: SECONDARY
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_32546_c7a9556cbf7
EAL: Probing VFIO support...
EAL: PCI device 0000:01:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 8086:1528 net_ixgbe
EAL: Cannot find resource for device
[ SetNetEnv: 361] No Ethernet port!

Any help is appreciated!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions