DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vipin Agrawal <vipin.agrawal@argyledata.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] dpdk_nic_bind giving error
Date: Fri, 23 Jan 2015 22:26:34 +0000	[thread overview]
Message-ID: <397E527E-DFA3-4648-9573-190EAA7B6FB9@argyledata.com> (raw)

I’m running on centos with kernel 3.18.3 and built the dpdk with gcc 4.7 and running with python 3.3

When trying to get status or even trying to bind to the eth0 port, I get the following error :

[root@linux-dt dpdk-1.8.0]# tools/dpdk_nic_bind.py --status
Traceback (most recent call last):
  File "tools/dpdk_nic_bind.py", line 536, in <module>
    main()
  File "tools/dpdk_nic_bind.py", line 532, in main
    get_nic_details()
  File "tools/dpdk_nic_bind.py", line 225, in get_nic_details
    dev_lines = check_output(["lspci", "-Dvmmn"]).splitlines()
  File "tools/dpdk_nic_bind.py", line 120, in check_output
    stderr=stderr).communicate()[0]
  File "/usr/lib64/python2.6/subprocess.py", line 642, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.6/subprocess.py", line 1234, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory


What am I doing wrong?



________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Thank you in advance for your cooperation.

________________________________

             reply	other threads:[~2015-01-23 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 22:26 Vipin Agrawal [this message]
2015-01-24  2:46 ` Neil Horman

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=397E527E-DFA3-4648-9573-190EAA7B6FB9@argyledata.com \
    --to=vipin.agrawal@argyledata.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).