DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] Unable to bind Virtio_pci in DPDK1.7
@ 2015-05-29  5:22 Dey, Souvik
  2015-05-29  5:34 ` Ouyang, Changchun
  0 siblings, 1 reply; 2+ messages in thread
From: Dey, Souvik @ 2015-05-29  5:22 UTC (permalink / raw)
  To: dev

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.

--
Regards,
Souvik

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dpdk-dev] Unable to bind Virtio_pci in DPDK1.7
  2015-05-29  5:22 [dpdk-dev] Unable to bind Virtio_pci in DPDK1.7 Dey, Souvik
@ 2015-05-29  5:34 ` Ouyang, Changchun
  0 siblings, 0 replies; 2+ messages in thread
From: Ouyang, Changchun @ 2015-05-29  5:34 UTC (permalink / raw)
  To: Dey, Souvik, dev


> -----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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-05-29  5:34 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-29  5:22 [dpdk-dev] Unable to bind Virtio_pci in DPDK1.7 Dey, Souvik
2015-05-29  5:34 ` Ouyang, Changchun

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).