On Fri, Nov 07, 2014 at 08:31:34PM +0530, Manoj Viswanath wrote: > Hi Bruce, > > I was not doing anything specific for binding the NICs to IGB_UIO (like > invoking "dpdk_nic_bind.py" script explicitly) when using my application > with DPDK 1.6.0. The e1000 devices assigned via virt-manager to the VM were > automatically getting picked up and initialized by IGB_UIO within each VM. > > The same is not working with DPDK 1.7.1 now. > > I tried exporting the "dpdk_nic_bind.py" script into my VM (running DPDK > 1.7.1) and tried to check the status. The emulated devices were shown as > neither bound to kernel nor to IGB_UIO as evident from below output:- > > <---------------------------------------------------------------------------------------------------> > Network devices using DPDK-compatible driver > ============================================ > <none> > > Network devices using kernel driver > =================================== > 0000:00:03.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio > > Other network devices > ===================== > 0000:00:04.0 '82540EM Gigabit Ethernet Controller' unused=igb_uio > 0000:00:05.0 '82540EM Gigabit Ethernet Controller' unused=igb_uio > <---------------------------------------------------------------------------------------------------> > > When i tried to forcefully bind the NICs using the "--bind=igb_uio" option
Was there any output of the dpdk_nic_bind script? What does the output of it with --status show afterwards? Regards, /Bruce
