* [dpdk-dev] TAP PMD does not work in 17.05
@ 2017-06-22 7:05 Chillance Zen
2017-06-23 11:28 ` Ferruh Yigit
0 siblings, 1 reply; 3+ messages in thread
From: Chillance Zen @ 2017-06-22 7:05 UTC (permalink / raw)
To: dev
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?
--
Linc @bjtu
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] TAP PMD does not work in 17.05
2017-06-22 7:05 [dpdk-dev] TAP PMD does not work in 17.05 Chillance Zen
@ 2017-06-23 11:28 ` Ferruh Yigit
2017-06-23 11:51 ` Pascal Mazon
0 siblings, 1 reply; 3+ messages in thread
From: Ferruh Yigit @ 2017-06-23 11:28 UTC (permalink / raw)
To: Chillance Zen, dev; +Cc: Pascal Mazon
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] TAP PMD does not work in 17.05
2017-06-23 11:28 ` Ferruh Yigit
@ 2017-06-23 11:51 ` Pascal Mazon
0 siblings, 0 replies; 3+ messages in thread
From: Pascal Mazon @ 2017-06-23 11:51 UTC (permalink / raw)
To: Ferruh Yigit, Chillance Zen, dev
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-06-23 11:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-22 7:05 [dpdk-dev] TAP PMD does not work in 17.05 Chillance Zen
2017-06-23 11:28 ` Ferruh Yigit
2017-06-23 11:51 ` Pascal Mazon
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).