From: Nagaprabhanjan Bellaru <nagp.lists@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Not able to access /dev/uioX from inside LXC
Date: Sat, 12 Nov 2016 20:02:20 +0530 [thread overview]
Message-ID: <CABDVJk_MA7Bb+uVvADodF++67tYue0k_oYNXa_6eNntQOM-FAg@mail.gmail.com> (raw)
Hi,
The instructions mentioned by Krishnamurthy here:
http://dpdk.org/ml/archives/dev/2014-October/006373.html
greatly helped to make progress on accessing PCI devices from with in the
container, however, DPDK is not able to open them because of privilege
issues. Has somebody been able to crack this issue? If so, can they please
show me the way to do it?
--
EAL: Detected 24 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
[New Thread 0x7fff8ece0700 (LWP 22134)]
EAL: PCI device 0000:06:00.0 on NUMA socket -1
EAL: probe driver: 8086:1583 rte_i40e_pmd
EAL: Cannot open /dev/uio0: Operation not permitted
EAL: Error - exiting with code: 1
Cause: Requested device 0000:06:00.0 cannot be used
[Thread 0x7ffff7fe7700 (LWP 22130) exited]
[Inferior 1 (process 22130) exited with code 01]
--
Thanks,
-nagp
next reply other threads:[~2016-11-12 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 14:32 Nagaprabhanjan Bellaru [this message]
2016-11-15 6:44 ` Nagaprabhanjan Bellaru
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_MA7Bb+uVvADodF++67tYue0k_oYNXa_6eNntQOM-FAg@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).