DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: "Dey, Souvik" <sodey@sonusnet.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Unable to bind Virtio_pci in DPDK1.7
Date: Fri, 29 May 2015 05:34:53 +0000	[thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F962511B6D95B@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <BN3PR0301MB12029C0101F02F7A6FC658F5DAC90@BN3PR0301MB1202.namprd03.prod.outlook.com>


> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Dey, Souvik
> Sent: Friday, May 29, 2015 1:22 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Unable to bind Virtio_pci in DPDK1.7
> 
> Hi All,
>                 I am currently facing a weird issue where I am not able to bind the
> virtio_pci device to igb_uio in DPDK1.7 on QEMU/KVM. I can see there are
> two fold issues.
> 1.The pci_unbind.py script where the virt_path is removed from 1.6 to 1.7
> version due to which the initial status is not able to show any interface name.
> 
> Network devices using DPDK-compatible driver
> ============================================
> <none>
> 
> Network devices using kernel driver
> ===================================
> 0000:00:03.0 'Virtio network device' if= drv=virtio-pci
> unused=virtio_pci,igb_uio
> 0000:00:04.0 'Virtio network device' if= drv=virtio-pci
> unused=virtio_pci,igb_uio
> 0000:00:05.0 'Virtio network device' if= drv=virtio-pci
> unused=virtio_pci,igb_uio
> 0000:00:06.0 'Virtio network device' if= drv=virtio-pci
> unused=virtio_pci,igb_uio
> 
> Other network devices
> =====================
> <none>
> 
> 
> 2. After correcting the above issue , I am stuck where the interface is failing
> to bind to igb_uio. I tried to bind the interface manually  to igb_uio but I am
> getting the following error
> 
> lspci -k
> 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device
>         Subsystem: Red Hat, Inc Device 0001
>         Kernel modules: virtio_pci
> 
> echo 0000:00:05.0 > /sys/bus/pci/drivers/igb_uio/bind
> -bash: echo: write error: No such device
> 
> Due to this the bind fails and the virtio_pmd is not able to take and my app is
> not coming up.
> EAL: PCI device 0000:00:03.0 on NUMA socket -1
> EAL:   probe driver: 1af4:1000 rte_virtio_pmd
> EAL:   0000:00:06.0 not managed by UIO driver, skipping
> EAL: Error - exiting with code: 1
>   Cause: No Ethernet ports - bye
> 
> I see lots of email threads on similar issue but none had the final conclusion.
> So can someone guide me on how to proceed further or get out of this error.
> 

Suggest you use the dpdk_nic_bind.py in recently released dpdk package or get it from dpdk.org repo.
I use it to bind virtio-pci device to igb_uio and after that, I bind it reversely from igb_uio back to virtio-pci again.
It works, don't find any issue.   

Thanks
Changchun

      reply	other threads:[~2015-05-29  5:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  5:22 Dey, Souvik
2015-05-29  5:34 ` Ouyang, Changchun [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=F52918179C57134FAEC9EA62FA2F962511B6D95B@shsmsx102.ccr.corp.intel.com \
    --to=changchun.ouyang@intel.com \
    --cc=dev@dpdk.org \
    --cc=sodey@sonusnet.com \
    /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).