From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: "Ravada, Dhanunjaya" <dr3662@intl.att.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] running dpdk in lxc-container
Date: Wed, 15 Mar 2017 15:58:35 +0000 [thread overview]
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361A0AE1A@lhreml501-mbs> (raw)
In-Reply-To: <7572B6BD2438064FA51D48FEEEDF180D35256C83@INHYDMBX03.intl.att.com>
Thanks Ravada
I've already resolve this issue by binding the devices in the host and mount the /dev/uiox/ in the lxc with mknod command
This is described here: http://dpdk.org/ml/archives/dev/2014-October/006373.html
But when I run my dpdk application I receive this error :
EAL: Cannot open /dev/uio0: Operation not permitted
Btw - I'm running as root
Best regards
avi
> -----Original Message-----
> From: Ravada, Dhanunjaya [mailto:dr3662@intl.att.com]
> Sent: Wednesday, 15 March, 2017 5:48 PM
> To: Avi Cohen (A)
> Subject: RE: running dpdk in lxc-container
>
> I think you don't have permissions. Can you try with sudo
>
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Avi Cohen (A)
> Sent: Wednesday, March 15, 2017 8:29 PM
> To: users@dpdk.org
> Subject: Re: [dpdk-users] running dpdk in lxc-container
>
> Hi,
> I've solved the original problem by simply installing pciutils But now I cannot
> bind to dpdk - and get this error:
>
> ./dpdk-devbind.py --bind=igb_uio 0000:04:00.0
> lspci: Unable to load libkmod resources: error -12
> lspci: Unable to load libkmod resources: error -12
> lspci: Unable to load libkmod resources: error -12
> lspci: Unable to load libkmod resources: error -12
> lspci: Unable to load libkmod resources: error -12
> lspci: Unable to load libkmod resources: error -12
> Error: unbind failed for 0000:04:00.0 - Cannot open
> /sys/bus/pci/drivers/ixgbe/unbind
>
> Best regards
> avi
>
> > -----Original Message-----
> > From: Avi Cohen (A)
> > Sent: Wednesday, 15 March, 2017 2:32 PM
> > To: users@dpdk.org
> > Subject: running dpdk in lxc-container
> >
> > Hello,
> > I'm trying to run dpdk in lxc-container .
> > But I failed to bind the nic to the dpdk driver (igb-uio), actually I
> > failed in the ./dpdk-devbind,py --status Is it possible to run dpdk in lxc-
> container ?
> >
> > I get this error:
> >
> > Traceback (most recent call last):
> > File "./dpdk-devbind.py", line 577, in <module>
> > main()
> > File "./dpdk-devbind.py", line 573, in main
> > get_nic_details()
> > File "./dpdk-devbind.py", line 249, in get_nic_details
> > dev_lines = check_output(["lspci", "-Dvmmn"]).splitlines()
> > File "./dpdk-devbind.py", line 125, in check_output
> > stderr=stderr).communicate()[0]
> > File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
> > errread, errwrite)
> > File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
> > raise child_exception
> > OSError: [Errno 2] No such file or directory
> >
> >
> > Best regards
> > avi
next prev parent reply other threads:[~2017-03-15 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 14:59 Avi Cohen (A)
[not found] ` <7572B6BD2438064FA51D48FEEEDF180D35256C83@INHYDMBX03.intl.att.com>
2017-03-15 15:58 ` Avi Cohen (A) [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-15 12:31 Avi Cohen (A)
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=B84047ECBD981D4B93EAE5A6245AA361A0AE1A@lhreml501-mbs \
--to=avi.cohen@huawei.com \
--cc=dr3662@intl.att.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).