DPDK patches and discussions
 help / color / mirror / Atom feed
From: Moon-Sang Lee <sang0627@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] sysfs permission problem when running dpdk app in lxc
Date: Fri, 9 Sep 2016 09:56:52 +0900	[thread overview]
Message-ID: <CAACK=XcN6jiCfogWRkN_=9Vd2VCRTk6rd2Ec=iS7LmYZf6w8Yw@mail.gmail.com> (raw)
In-Reply-To: <CAACK=XeMZM0nvGk5UQh8G-uM_JFd8j_x92mFP1Z+WhHyHZR=zg@mail.gmail.com>

I found many other guys face the same issue as mine, but no replies to
their question.
Anyway, there are three major option groups including apparmor, seccome,
and cgroup.
It seems that some security options of lxc prevent my DPDK app from opening
sysfs file in RW mode.
I changed lxc.aa_profile to unconfied, and that resolved my issue.



On Mon, Sep 5, 2016 at 2:33 PM, Moon-Sang Lee <sang0627@gmail.com> wrote:

>
> I'm using ubuntu 16.04 LTS as my host and installed lxd on it.
> When I try to run my dpdk(2.2.0) app in the container, I got following
> error message.
>
> EAL: lcore 9 is ready (tid=17fd700;cpuset=[9])
> EAL: lcore 3 is ready (tid=c915700;cpuset=[3])
> EAL: lcore 11 is ready (tid=ffc700;cpuset=[11])
> EAL: lcore 5 is ready (tid=27ff700;cpuset=[5])
> EAL: lcore 7 is ready (tid=1ffe700;cpuset=[7])
> EAL: lcore 13 is ready (tid=7fb700;cpuset=[13])
> EAL: PCI device 0000:06:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:10e8 rte_igb_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:06:00.1 on NUMA socket -1
> EAL:   probe driver: 8086:10e8 rte_igb_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:07:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:10e8 rte_igb_pmd
> EAL: Cannot open /sys/class/uio/uio0/device/config: Permission denied
> EAL: Error - exiting with code: 1
>   Cause: Requested device 0000:07:00.0 cannot be used
>
>
>
> However, it seems ok of the permission when I list those files.
> I appreciate any comments.
>
> root@test4:~# cat /proc/mounts |grep sysfs
> sysfs /sys sysfs rw,relatime 0 0
> root@test4:~# ls -al /sys/class/uio/uio0/device/config
> -rw-r--r-- 1 root root 4096 Sep  5 04:56 /sys/class/uio/uio0/device/config
> root@test4:~# ls -al /dev/uio0
> crw-rw-rw- 1 root root 243, 0 Sep  5 04:16 /dev/uio0
> root@test4:~#
>
>
>
> --
> Moon-Sang Lee, SW Engineer
> Email: sang0627@gmail.com
> Wisdom begins in wonder. *Socrates*
>



-- 
Moon-Sang Lee, SW Engineer
Email: sang0627@gmail.com
Wisdom begins in wonder. *Socrates*

      reply	other threads:[~2016-09-09  0:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  5:33 Moon-Sang Lee
2016-09-09  0:56 ` Moon-Sang Lee [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='CAACK=XcN6jiCfogWRkN_=9Vd2VCRTk6rd2Ec=iS7LmYZf6w8Yw@mail.gmail.com' \
    --to=sang0627@gmail.com \
    --cc=dev@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).