From: Chris Paquin <cpaquin@redhat.com>
To: Sagar Singha <singha.sagar09@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Unable to run l2fwd code
Date: Fri, 1 Sep 2017 10:43:10 -0400 [thread overview]
Message-ID: <CAAMYPe50efO0=MxNm0Vk8vY05Gi4TnwUGDxXku2aZAUdEY8LWg@mail.gmail.com> (raw)
In-Reply-To: <CAKXXrHd1uXuOu2T5nSUa=Y13Dq8LRDQ_NAVa=U=FR+_ZedijRQ@mail.gmail.com>
Can you share the output of "../usertools/dpdk_devbind.py -s"?
CHRISTOPHER PAQUIN
SENIOR CLOUD CONSULTANT, RHCE, RHCSA-OSP
Red Hat <https://www.redhat.com/>
M: 770-906-7646
<https://red.ht/sig>
On Fri, Sep 1, 2017 at 7:16 AM, Sagar Singha <singha.sagar09@gmail.com>
wrote:
> Hi,
>
> I am using VMXNET3 type VM .OS distro=UBUNTU14.04.
> My VM is having only one core CPU and 1 GB RAM
>
> I have followed the below process to configure dpdk after downloading the
> source code:
>
> 1.make config T=x86_64-native-linuxapp-gcc
> 2.make
> 3.sudo modprobe uio
> sudo insmod build/kmod/igb_uio.ko
> modprobe vfio
> modprobe uio_pci_generic
> modprobe vfio-pci
> 4.echo 1024 >
> /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
> 5.sudo mkdir /mnt/huge
> sudo mount -t hugetlbfs nodev /mnt/huge
> 6.echo 1 > /sys/module/vfio/parameters/enable_unsafe_noiommu_mode
> 7../usertools/dpdk_devbind.py --bind=vfio-pci --force ens160
>
>
> after that I am running the below command for running the l2fwd
>
> l2fwd c1 n4 --no-huge -- -p1
>
> Then the error is like below:
>
> EAL: Detected 1 lcore(s)
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: Started without hugepages support, physical addresses not available
> EAL: PCI device 0000:03:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 15ad:7b0 net_vmxnet3
> EAL: PCI device 0000:0b:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 15ad:7b0 net_vmxnet3
> EAL: using IOMMU type 8 (No-IOMMU)
> EAL: Ignore mapping IO port bar(3) addr: 5001
> EAL: PCI device 0000:13:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 15ad:7b0 net_vmxnet3
> MAC updating enabled
> Notice: odd number of ports in portmask.
> Lcore 0: RX port 0
> Initializing port 0... In rte_eth_dev_start
> From return diag
> EAL: Error - exiting with code: 1
> Cause: rte_eth_dev_start:err=-22, port=0
>
> Can any one please help here!!
> Thanks i advance !!!
>
>
> --
> Thanks & Regards,
> Sagar Singha
> Contact:7416733224
> 9475209510
>
next prev parent reply other threads:[~2017-09-01 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 11:16 Sagar Singha
2017-09-01 14:43 ` Chris Paquin [this message]
2017-09-01 15:25 ` Sagar Singha
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='CAAMYPe50efO0=MxNm0Vk8vY05Gi4TnwUGDxXku2aZAUdEY8LWg@mail.gmail.com' \
--to=cpaquin@redhat.com \
--cc=singha.sagar09@gmail.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).