Re: [dpdk-users] port 0 not present on board error

Re: [dpdk-users] port 0 not present on board error

[Hristo.Trifonov]

Not showing "Active" status is perfectly normal.

The problem here is that you will probably need to supply extra parameters.
This is from your previous posts:

pragash at revvit<http://dpdk.org/ml/listinfo/users>:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 0-4 --no-huge -- -p 0x1

Try changing to:

pragash at revvit<http://dpdk.org/ml/listinfo/users>:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 1-4(core 0 is usually master lcore) --no-huge -- -p 0x3 -L(optional) -config="(0,0,1),(1,0,2)" --parse-type



This worked for me. You can check the docs here http://dpdk.org/doc/guides/sample_app_ug/l3_forward.html for all options.


If you don't specify the "config" option the app won't even start returning the "check port config" error. You must also supply the "-parse-type" cmd parameter otherwise app complaints and fails to start with the following error "port 0 cannot parse packet type, please add -parse-type"

Hristo T.

Re: [dpdk-users] port 0 not present on board error

[Pragash Vijayaragavan]

Hi,

I am still getting some errors;

port 0 is not present on the board.

pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 1-4
--no-huge -- -p 0x3 -L --config="(0,0,1),(1,0,2)" --ipv6 --parse-ptype
EAL: Detected 20 lcore(s)
EAL: Probing VFIO support...
EAL: Started without hugepages support, physical addresses not available
EAL: PCI device 0000:02:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:02:00.0 cannot be used
EAL: PCI device 0000:02:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:04:00.0 cannot be used
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:08:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:08:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
L3FWD: Longest-prefix match selected
L3FWD: IPV6 is specifiednsoft parse-ptype is enabled
port 0 is not present on the board
EAL: Error - exiting with code: 1
  Cause: check_port_config failed


Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662


On Mon, Dec 11, 2017 at 6:21 AM, Hristo.Trifonov <Hristo.Trifonov@ul.ie>
wrote:

> Not showing "Active" status is perfectly normal.
>
> The problem here is that you will probably need to supply extra parameters.
> This is from your previous posts:
>
> pragash at revvit<http://dpdk.org/ml/listinfo/users>:~/dpdk-stable-17.05.2/examples/l3fwd/build$
> ./l3fwd -l 0-4 --no-huge -- -p 0x1
>
> Try changing to:
>
> pragash at revvit<http://dpdk.org/ml/listinfo/users>:~/dpdk-stable-17.05.2/examples/l3fwd/build$
> ./l3fwd -l 1-4(core 0 is usually master lcore) --no-huge -- -p 0x3
> -L(optional) -config="(0,0,1),(1,0,2)" --parse-type
>
>
>
> This worked for me. You can check the docs here
> http://dpdk.org/doc/guides/sample_app_ug/l3_forward.html for all options.
>
>
> If you don't specify the "config" option the app won't even start
> returning the "check port config" error. You must also supply the
> "-parse-type" cmd parameter otherwise app complaints and fails to start
> with the following error "port 0 cannot parse packet type, please add
> -parse-type"
>
> Hristo T.
>

Re: [dpdk-users] port 0 not present on board error

[Pragash Vijayaragavan]

I tried to debug by printing the check_port_config function

and printed the nb_ports parameter, -> this is 0

so i guess no ports are bind to the dpdk driver since its still showing
net_i40e in probe driver.

Should i do any config to solve this error.
i am using igb_uio and the ports are bind correctly, i bind using the
dpdk_dev_bind script.


pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 1-19
--no-huge -- -p 0x07 -L --config="(0,0,1),(1,0,2)" --ipv6 --parse-ptype
EAL: Detected 20 lcore(s)
EAL: Probing VFIO support...
EAL: Started without hugepages support, physical addresses not available
EAL: PCI device 0000:02:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:02:00.0 cannot be used
EAL: PCI device 0000:02:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:04:00.0 cannot be used
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:08:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:08:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
L3FWD: Longest-prefix match selected
L3FWD: IPV6 is specifiednsoft parse-ptype is enabled
ports   ---- 0
port 0 is not present on the board
EAL: Error - exiting with code: 1
  Cause: check_port_config failed



Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662


On Mon, Dec 11, 2017 at 4:24 PM, Pragash Vijayaragavan <pxv3620@g.rit.edu>
wrote:

> Hi,
>
> I am still getting some errors;
>
> port 0 is not present on the board.
>
> pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 1-4
> --no-huge -- -p 0x3 -L --config="(0,0,1),(1,0,2)" --ipv6 --parse-ptype
> EAL: Detected 20 lcore(s)
> EAL: Probing VFIO support...
> EAL: Started without hugepages support, physical addresses not available
> EAL: PCI device 0000:02:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: Requested device 0000:02:00.0 cannot be used
> EAL: PCI device 0000:02:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: Requested device 0000:04:00.0 cannot be used
> EAL: PCI device 0000:04:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: PCI device 0000:08:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:08:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> L3FWD: Longest-prefix match selected
> L3FWD: IPV6 is specifiednsoft parse-ptype is enabled
> port 0 is not present on the board
> EAL: Error - exiting with code: 1
>   Cause: check_port_config failed
>
>
> Thanks,
>
> Pragash Vijayaragavan
> Grad Student at Rochester Institute of Technology
> email : pxv3620@rit.edu
> ph : 585 764 4662 <(585)%20764-4662>
>
>
> On Mon, Dec 11, 2017 at 6:21 AM, Hristo.Trifonov <Hristo.Trifonov@ul.ie>
> wrote:
>
>> Not showing "Active" status is perfectly normal.
>>
>> The problem here is that you will probably need to supply extra
>> parameters.
>> This is from your previous posts:
>>
>> pragash at revvit<http://dpdk.org/ml/listinfo/users>:~/dpdk-stable-17.05.2/examples/l3fwd/build$
>> ./l3fwd -l 0-4 --no-huge -- -p 0x1
>>
>> Try changing to:
>>
>> pragash at revvit<http://dpdk.org/ml/listinfo/users>:~/dpdk-stable-17.05.2/examples/l3fwd/build$
>> ./l3fwd -l 1-4(core 0 is usually master lcore) --no-huge -- -p 0x3
>> -L(optional) -config="(0,0,1),(1,0,2)" --parse-type
>>
>>
>>
>> This worked for me. You can check the docs here
>> http://dpdk.org/doc/guides/sample_app_ug/l3_forward.html for all options.
>>
>>
>> If you don't specify the "config" option the app won't even start
>> returning the "check port config" error. You must also supply the
>> "-parse-type" cmd parameter otherwise app complaints and fails to start
>> with the following error "port 0 cannot parse packet type, please add
>> -parse-type"
>>
>> Hristo T.
>>
>
>

Re: [dpdk-users] port 0 not present on board error

[Stephen Hemminger]

On Mon, 11 Dec 2017 16:24:18 -0500
Pragash Vijayaragavan <pxv3620@rit.edu> wrote:

> $ ./l3fwd -l 1-4
> --no-huge -- -p 0x3 -L --config="(0,0,1),(1,0,2)" --ipv6 --parse-ptype
> EAL: Detected 20 lcore(s)
> EAL: Probing VFIO support...
> EAL: Started without hugepages support, physical addresses not available

Try setting up huge pages, that can help.

> EAL: PCI device 0000:02:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: Requested device 0000:02:00.0 cannot be used

Since you are using VFIO, that implies IOMMU support.
With IOMMU on some systems the IOMMU channels overlap groups.
See Linux kernel documentation vfio.txt for more information on how
VFIO works and how to map out groups.

When a device is in a group with another device, you must
assign or unbind both devices in order for VFIO-PCI to work.
On one system, I had unbind (which disabled) the on board NIC
in order to use VFIO with a 10G or 40G device in the PCI-E slot
since both NIC's shared the same group.

Unfortunately, the easiest solution is just to find another
system since this is a wiring/motherboard issue not something
controlled by OS or BIOS.


> EAL: PCI device 0000:02:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: Requested device 0000:04:00.0 cannot be used
> EAL: PCI device 0000:04:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: PCI device 0000:08:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:08:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> L3FWD: Longest-prefix match selected
> L3FWD: IPV6 is specifiednsoft parse-ptype is enabled
> port 0 is not present on the board

Re: [dpdk-users] port 0 not present on board error

[Hristo.Trifonov]

Unfortunately I don't have XL710 NIC available to test.

Off the top of my head:

-          Is this an issue only with the l3fwd app?

-          Did you try to run testpmd, skeleton or l2fwd?

-          Is the card working properly with the kernel driver?

-          Did you try previous version of dpdk?

Hristo T.

Re: [dpdk-users] port 0 not present on board error

[Pragash Vijayaragavan]

Hi,


-          Is this an issue only with the l3fwd app?
                                 No every app which requires ports is
having an issue

-          Did you try to run testpmd, skeleton or l2fwd?

                                Yea same issue

-          Is the card working properly with the kernel driver?
                                Yes it works fine

-          Did you try previous version of dpdk?
                                 Which version should i try? I tried latest
17.11 and stable 17.05 so far


Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662


On Tue, Dec 12, 2017 at 9:02 AM, Hristo.Trifonov <Hristo.Trifonov@ul.ie>
wrote:

> Unfortunately I don't have XL710 NIC available to test.
>
> Off the top of my head:
>
> -          Is this an issue only with the l3fwd app?
>
> -          Did you try to run testpmd, skeleton or l2fwd?
>
> -          Is the card working properly with the kernel driver?
>
> -          Did you try previous version of dpdk?
>
> Hristo T.
>

Re: [dpdk-users] port 0 not present on board error

[Hristo.Trifonov]

Please use only 2 ports with 1RX queue and 1 TX queue each to get l3fwd running. Try with these 2 below.
0000:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio unused=vfio-pci
0000:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio unused=vfio-pci

You can use more ports/queues but then you'll have to change the -config option depending on how many cores do you want to use.

The cmd that I've provided in my previous post is specifically for 2 ports with 1RX and TX queue each and 2 cores.

I suggest that you restart your machine, if possible, to unbind all ports from igb_uio and start from scratch.
Otherwise use the dpdk-seup.py script to do the clean-up.

Hristo T.

Re: [dpdk-users] port 0 not present on board error

[Pragash Vijayaragavan]

This did not work as well.

Below is the error and config outputs


pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ sudo  ./l3fwd -c
0xE --no-huge -- -p 0x03 -L --config="(0,0,1),(1,0,2)" --parse-ptype
EAL: Detected 20 lcore(s)
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: Started without hugepages support, physical addresses not available
EAL: PCI device 0000:02:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:02:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:04:00.0 cannot be used
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:04:00.1 cannot be used
EAL: PCI device 0000:08:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:08:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
L3FWD: Longest-prefix match selected
soft parse-ptype is enabled
ports   ---- 0
port 0 is not present on the board
EAL: Error - exiting with code: 1
  Cause: check_port_config failed



Network devices using DPDK-compatible driver
============================================
0000:04:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
unused=vfio-pci
0000:04:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
unused=vfio-pci

Network devices using kernel driver
===================================
0000:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' if=eth13
drv=i40e unused=igb_uio,vfio-pci
0000:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' if=eth12
drv=i40e unused=igb_uio,vfio-pci
0000:08:00.0 'I350 Gigabit Network Connection 1521' if=eth0 drv=igb
unused=igb_uio,vfio-pci *Active*
0000:08:00.1 'I350 Gigabit Network Connection 1521' if=eth2 drv=igb
unused=igb_uio,vfio-pci

Other Network devices
=====================
<none>




Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662


On Tue, Dec 12, 2017 at 7:47 AM, Hristo.Trifonov <Hristo.Trifonov@ul.ie>
wrote:

> Please use only 2 ports with 1RX queue and 1 TX queue each to get l3fwd
> running. Try with these 2 below.
> 0000:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
> unused=vfio-pci
> 0000:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
> unused=vfio-pci
>
> You can use more ports/queues but then you'll have to change the -config
> option depending on how many cores do you want to use.
>
> The cmd that I've provided in my previous post is specifically for 2 ports
> with 1RX and TX queue each and 2 cores.
>
> I suggest that you restart your machine, if possible, to unbind all ports
> from igb_uio and start from scratch.
> Otherwise use the dpdk-seup.py script to do the clean-up.
>
> Hristo T.
>
>

Re: [dpdk-users] port 0 not present on board error

[Hristo.Trifonov]

If your nb_ports = 0  shows that you haven't bind/provided any ports to dpdk.

Just verify that the ports that you want to use with dpdk (igb_uio) are available on the machine.
This means that they are not used for anything else but dpdk.

Before you attempt to bind any ports to igb_uio, from the terminal check what ports are available on the machine using nmcli d or any other utility.
Load the igb_uio kernel module using the dpdk_setup  script in dpdk/usertools
Then use the dpdk_dev_bind or dpdk_setup  script to bind the selected ports to igb_uio.
Verify that the ports are using the igb_uio with the dpdk_setup  script. There is an option there for that.

If you are using 2 ports (-p 0x3), use 2 lcores (-c 0xE) core 2 and core 3 in this case.
Complete the cmd like this:
pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$<mailto:pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$> ./l3fwd -c 0xE --no-huge -- -p 0x03 -L --config="(0,0,1),(1,0,2)" --parse-ptype

If you want to use more lcores you must then change the -config option to reflect the situation in terms of (port,queue,lcore)

Hristo T.

Re: [dpdk-users] port 0 not present on board error

[Pragash Vijayaragavan]

Hi,

im still getting the same error

here is my dpdk_setup output

Is it possible that my NICs dont support running dpdk.


Network devices using DPDK-compatible driver
============================================
0000:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
unused=vfio-pci
0000:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
unused=vfio-pci
0000:04:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
unused=vfio-pci
0000:04:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
unused=vfio-pci

Network devices using kernel driver
===================================
0000:08:00.0 'I350 Gigabit Network Connection 1521' if=eth0 drv=igb
unused=igb_uio,vfio-pci *Active*
0000:08:00.1 'I350 Gigabit Network Connection 1521' if=eth2 drv=igb
unused=igb_uio,vfio-pci

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>

Press enter to continue ...


Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662


On Tue, Dec 12, 2017 at 5:54 AM, Hristo.Trifonov <Hristo.Trifonov@ul.ie>
wrote:

> If your nb_ports = 0  shows that you haven't bind/provided any ports to
> dpdk.
>
> Just verify that the ports that you want to use with dpdk (igb_uio) are
> available on the machine.
> This means that they are not used for anything else but dpdk.
>
> Before you attempt to bind any ports to igb_uio, from the terminal check
> what ports are available on the machine using nmcli d or any other utility.
> Load the igb_uio kernel module using the dpdk_setup  script in
> dpdk/usertools
> Then use the dpdk_dev_bind or dpdk_setup  script to bind the selected
> ports to igb_uio.
> Verify that the ports are using the igb_uio with the dpdk_setup  script.
> There is an option there for that.
>
> If you are using 2 ports (-p 0x3), use 2 lcores (-c 0xE) core 2 and core 3
> in this case.
> Complete the cmd like this:
> pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$<mailto:
> pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$> ./l3fwd -c
> 0xE --no-huge -- -p 0x03 -L --config="(0,0,1),(1,0,2)" --parse-ptype
>
> If you want to use more lcores you must then change the -config option to
> reflect the situation in terms of (port,queue,lcore)
>
> Hristo T.
>

Re: [dpdk-users] port 0 not present on board error

[Hristo.Trifonov]

Hi Pragash,

How many ports are assigned to dpdk?
Why is there only 1 port in the portmask (-p 0x1)?

Dpdk would typically use pair(s) of ports.
First port(0x1) in the portmask(0x3) is usually ingress traffic and the second port(0x2) of the pair is the egress traffic.
Try with -p 0x3 portmask but make sure you have at least 2 ports already assigned for use with a dpdk app.
If you have more than 2 ports adjust the portmask hex number to reflect the situation.

Hristo T.

Re: [dpdk-users] port 0 not present on board error

[Pragash Vijayaragavan]

Hi ,

I have attached 2 ports to dpdk, and i tried -p 0x3 as well.

I have noticed that the ports are not showing the "Active" status, is that
an issue?

Below is the output from dpdk-status

pragash@revvit:~/dpdk-stable-17.05.2/usertools$ dpdk-devbind --status

Network devices using DPDK-compatible driver
============================================
0000:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583'
drv=uio_pci_generic unused=
0000:04:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583'
drv=uio_pci_generic unused=

Network devices using kernel driver
===================================
0000:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' if=eth12
drv=i40e unused=uio_pci_generic
0000:04:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' if=eth10
drv=i40e unused=uio_pci_generic
0000:08:00.0 'I350 Gigabit Network Connection 1521' if=eth0 drv=igb
unused=uio_pci_generic *Active*
0000:08:00.1 'I350 Gigabit Network Connection 1521' if=eth2 drv=igb
unused=uio_pci_generic


Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662


On Fri, Dec 8, 2017 at 7:11 AM, Hristo.Trifonov <Hristo.Trifonov@ul.ie>
wrote:

> Hi Pragash,
>
> How many ports are assigned to dpdk?
> Why is there only 1 port in the portmask (-p 0x1)?
>
> Dpdk would typically use pair(s) of ports.
> First port(0x1) in the portmask(0x3) is usually ingress traffic and the
> second port(0x2) of the pair is the egress traffic.
> Try with -p 0x3 portmask but make sure you have at least 2 ports already
> assigned for use with a dpdk app.
> If you have more than 2 ports adjust the portmask hex number to reflect
> the situation.
>
> Hristo T.
>

[dpdk-users] port 0 not present on board error

[Pragash Vijayaragavan]

Hi Guys,

I am trying to run the l3fwd dpdk app on my machine.

I am getting the following error, can someone help me, Thanks.

pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 0-4
--no-huge -- -p 0x1
EAL: Detected 20 lcore(s)
EAL: Probing VFIO support...
EAL: Started without hugepages support, physical addresses not available
EAL: PCI device 0000:02:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:02:00.0 cannot be used
EAL: PCI device 0000:02:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:04:00.0 cannot be used
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:08:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:08:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
L3FWD: LPM or EM none selected, default LPM on
port 0 is not present on the board
EAL: Error - exiting with code: 1
  Cause: check_port_config failed




Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662

Re: [dpdk-users] port 0 not present on board error

[Dave Boutcher]

Are you running as root (sudo)?

Dave B

On Dec 7, 2017, at 10:01 PM, Pragash Vijayaragavan <pxv3620@rit.edu<mailto:pxv3620@rit.edu>> wrote:

Hi Guys,

I am trying to run the l3fwd dpdk app on my machine.

I am getting the following error, can someone help me, Thanks.

pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 0-4
--no-huge -- -p 0x1
EAL: Detected 20 lcore(s)
EAL: Probing VFIO support...
EAL: Started without hugepages support, physical addresses not available
EAL: PCI device 0000:02:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:02:00.0 cannot be used
EAL: PCI device 0000:02:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:04:00.0 cannot be used
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:08:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:08:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
L3FWD: LPM or EM none selected, default LPM on
port 0 is not present on the board
EAL: Error - exiting with code: 1
 Cause: check_port_config failed




Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu<mailto:pxv3620@rit.edu>
ph : 585 764 4662

Re: [dpdk-users] port 0 not present on board error

[Pragash Vijayaragavan]

Hi Dave,

I tried running as root, that didn work as well.

Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662


On Thu, Dec 7, 2017 at 11:18 PM, Dave Boutcher <dboutcher@ocient.com> wrote:

> Are you running as root (sudo)?
>
> Dave B
>
> On Dec 7, 2017, at 10:01 PM, Pragash Vijayaragavan <pxv3620@rit.edu>
> wrote:
>
> Hi Guys,
>
> I am trying to run the l3fwd dpdk app on my machine.
>
> I am getting the following error, can someone help me, Thanks.
>
> pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 0-4
> --no-huge -- -p 0x1
> EAL: Detected 20 lcore(s)
> EAL: Probing VFIO support...
> EAL: Started without hugepages support, physical addresses not available
> EAL: PCI device 0000:02:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: Requested device 0000:02:00.0 cannot be used
> EAL: PCI device 0000:02:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: Requested device 0000:04:00.0 cannot be used
> EAL: PCI device 0000:04:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: PCI device 0000:08:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:08:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> L3FWD: LPM or EM none selected, default LPM on
> port 0 is not present on the board
> EAL: Error - exiting with code: 1
>  Cause: check_port_config failed
>
>
>
>
> Thanks,
>
> Pragash Vijayaragavan
> Grad Student at Rochester Institute of Technology
> email : pxv3620@rit.edu
> ph : 585 764 4662 <(585)%20764-4662>
>
>