DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pascal Mazon <pascal.mazon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Chillance Zen <chillancezen@gmail.com>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] TAP PMD does not work in 17.05
Date: Fri, 23 Jun 2017 13:51:13 +0200	[thread overview]
Message-ID: <7a9efc06-dfc5-f264-d84b-9636cd698382@6wind.com> (raw)
In-Reply-To: <2dbba168-bd9a-fa30-b72f-41b2b1015cf3@intel.com>

Hi Chillance, Ferruh,

Can you give the complete command line you used, with output? 
(typically, are you using the remote feature)

As Ferruh said, it may be that you don't have the module loaded.
However in that case there should have been an error message earlier, 
like "Unable to create TAP interface". Hence the need for a complete trace.

What's your kernel version?

Best regards,
Pascal


On 06/23/2017 01:28 PM, Ferruh Yigit wrote:
> On 6/22/2017 8:05 AM, Chillance Zen wrote:
>> it always says something like this:
>>
>> PMD: tap1234: ioctl(35092) failed with error: No such device
>> PMD: Add queue to TAP tap1234 for qid 0
>> PMD: tap1234: ioctl(35108) failed with error: Cannot assign requested
>> address
>> PMD: tun_alloc(tap1234, 0) failed
>> PMD: tap1234: ioctl(35092) failed with error: No such device
>>
>> did any one ever meet this before?
>>
> Cc: Pascal
>
> I tried with latest code and 17.05 release and not observed the error.
>
> - Is this released 17.05 or any stable release version?
> - Is tun kernel module inserted?

      reply	other threads:[~2017-06-23 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22  7:05 Chillance Zen
2017-06-23 11:28 ` Ferruh Yigit
2017-06-23 11:51   ` Pascal Mazon [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=7a9efc06-dfc5-f264-d84b-9636cd698382@6wind.com \
    --to=pascal.mazon@6wind.com \
    --cc=chillancezen@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).