From: Nagaprabhanjan Bellaru <nagp.lists@gmail.com>
To: users@dpdk.org
Subject: Re: [dpdk-users] Not able to access uio0/device/config from LXC
Date: Mon, 14 Mar 2016 08:33:46 +0530 [thread overview]
Message-ID: <CABDVJk-scwDOq3Z5sjVo_CSdoC47vWWSAcyvP4PDf3NYt97NYg@mail.gmail.com> (raw)
In-Reply-To: <CABDVJk964Leu-hgtuBvUkvFr_Og_i1MP5cu6AO2Z2CMk21PqRA@mail.gmail.com>
I have tried everything from 400 to 777 (rwx permissions on the config
file) on the host (which gets reflected in the container as well), but
still EAL complains it cannot open the file. Any ideas/workarounds for
this issue, please?. If I do it from the host, it works fine..
--
EAL: Cannot open /sys/class/uio/uio0/device/config: Permission denied
EAL: Error - exiting with code: 1
Cause: Requested device 0000:00:19.0 cannot be used
--
Thanks,
-nagp
On Thu, Mar 10, 2016 at 4:32 PM, Nagaprabhanjan Bellaru
<nagp.lists@gmail.com> wrote:
> Sorry, I was referring to this thread:
> http://dpdk.org/ml/archives/dev/2014-October/006373.html
>
> -nagp
>
> On Thu, Mar 10, 2016 at 4:17 PM, Nagaprabhanjan Bellaru
> <nagp.lists@gmail.com> wrote:
>> I have followed the steps mentioned in this thread:
>>
>>
>> to create a uio0, but EAL complains about the following:
>> --
>> EAL: Cannot open /sys/class/uio/uio0/device/config: Permission denied
>> EAL: Error - exiting with code: 1
>> Cause: Requested device 0000:00:19.0 cannot be used
>> --
>>
>> even though I run as a root user and have all the rw permissions. Can
>> anybody tell me what else I could be missing?
>>
>> Thanks,
>> -nagp
prev parent reply other threads:[~2016-03-14 3:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 10:47 Nagaprabhanjan Bellaru
2016-03-10 11:02 ` Nagaprabhanjan Bellaru
2016-03-14 3:03 ` Nagaprabhanjan Bellaru [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=CABDVJk-scwDOq3Z5sjVo_CSdoC47vWWSAcyvP4PDf3NYt97NYg@mail.gmail.com \
--to=nagp.lists@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).