From: Ferruh Yigit <ferruh.yigit@intel.com>
To: hy_gzr <hy_gzr@163.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] example/kni failed
Date: Fri, 6 Dec 2019 10:07:14 +0000 [thread overview]
Message-ID: <aa9ad8cc-d586-6b7b-c4ac-b51263e6b6eb@intel.com> (raw)
In-Reply-To: <1cb2fff8.a3a2.16ed5aed211.Coremail.hy_gzr@163.com>
On 12/5/2019 10:50 AM, hy_gzr wrote:
> when I run the example/kni -l0-4 -- -P -p1 -m --config="(0,1,2)" in my physical machine,
> I don't get the dpdk virtual networke interface vEth(N) by ifconfig and the virtual interface is not active.
> but, I run the example in vm (linux in vmware),I can get a active virtual interface,
> so,,,why is not active in physical machin ? thanks!
> dmesg of insmod igb_uio:
> [ 634.971691] igb_uio: loading out-of-tree module taints kernel.
> [ 634.971898] igb_uio: module verification failed: signature and/or required key missing - tainting kernel
> [ 634.972563] igb_uio: Use MSIX interrupt by default
> [ 635.250107] igb 0000:02:00.0: removed PHC on eth0
> [ 635.318925] igb_uio 0000:02:00.0: mapping 1K dma=0x82cae2000 host=ffff99a96cae2000
> [ 635.318950] igb_uio 0000:02:00.0: unmapping 1K dma=0x82cae2000 host=ffff99a96cae2000
>
>
>
> dmesg of run example kni
> [ 978.094385] igb_uio 0000:02:00.0: irq 35 for MSI/MSI-X
> [ 978.094435] igb_uio 0000:02:00.0: uio device registered with irq 35
> [ 978.402505] rte_kni: Creating kni...
> [ 1003.513392] rte_kni: Successfully release kni named vEth0
>
>
> OS:centos 7.2.1511
> kernel 3.10.0-1062.4.3.el7.x86_64
> network:I350 Gigabit Network Connection 1521
> thanks!
>
>
Hi hy_gzr,
It is working fine in my environment. Can you please run with
'--log-level=lib.eal:debug' eal argument and shared the logs? Specially
interested in line with 'IOVA' keyword, since that is the change in last release.
Regards,
ferruh
prev parent reply other threads:[~2019-12-06 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 10:50 hy_gzr
2019-12-06 10:07 ` Ferruh Yigit [this message]
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=aa9ad8cc-d586-6b7b-c4ac-b51263e6b6eb@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hy_gzr@163.com \
/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).