Glad to hear that you solved the problem. What you have are Intel NIC - 82540em. The driver igb_uio should work for this - which is what you have. I am confused as to why you said that you were using Broadcom Nextreme card
Anyways, it is good to hear that you were able to rectify the issue. On Wed, Nov 15, 2017 at 4:40 AM, 王嵘 <[email protected]> wrote: > > hi, I solved the NIC bind problem. > I checked the log found that > netdev_dpdk|ERR|Interface dpdk-eth2(rxq:1 txq:3) configure error: Invalid > argument > so, I changed the rxq of the NIC to 3 by "options:n_rxq=3", and it works. > ^^ > > I tested the ovs2.8-dpdk in another VM of Centos7, but the "Permission > denied" problem still exists. > Here is the results of the commands you asked to execute, > > [root@localhost ~]# lshw -c network -businfo > Bus info Device Class Description > ======================================================== > pci@0000:00:03.0 network Virtio network device > virtio@0 eth0 network Ethernet interface > pci@0000:00:09.0 network 82540EM Gigabit Ethernet > Controller > pci@0000:00:0a.0 ens10 network 82540EM Gigabit Ethernet > Controller > br0 network Ethernet interface > ovs-netdev network Ethernet interface > virbr0-nic network Ethernet interface > virbr0 network Ethernet interface > [root@localhost ~]# lspci | egrep -i --color 'network|ethernet' > 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device > 00:09.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet > Controller (rev 03) > 00:0a.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet > Controller (rev 03) > [root@localhost ~]# lsmod | grep uio > igb_uio 13224 1 > uio 19259 3 igb_uio > > > > 在 2017-11-15 04:29:34，"Shivaram Mysore" <[email protected]> 写道： > > What is the output of the following commands: > > > lshw -c network -businfo > > lspci | egrep -i --color 'network|ethernet' > > lsmod | grep uio > > /sbin/dpdk-devbind --status > > > On Mon, Nov 13, 2017 at 9:29 PM, 王嵘 <[email protected]> wrote: > >> I just want to use ovs-2.8 for userspace connection-track, and I choose >> the latest LST DPDK 1705. >> But, you mean theres is something like broadcom-uio.ko when using >> broadcom NIC? >> I just have changed the config/common_base: >> >> CONFIG_RTE_LIBRTE_BNX2X_PMD=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=y >> CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_PERIODIC=y >> >> >> >> >> 在 2017-11-14 12:49:44，"Shivaram Mysore" <[email protected]> 写道： >> >> Is there a specific reason as to why you would want to use this version >> of DPDK? I have never had to check permission. >> >> Also, igb is mainly for Intel NICs. You are using a Broadcom NIC - >> http://dpdk.org/doc/guides/nics/bnxt.html for driver info. I think what >> you have is a misconfiguration. >> >> You may want to check out the scripts here https://github.com/shivar >> ammysore/faucetsdn-intel/tree/master/src/ubuntu/zesty/ovs_281 - to setup >> and configure DPDK. I have only used Intel NICs. >> >> Cheers! >> >> On Mon, Nov 13, 2017 at 6:50 PM, 王嵘 <[email protected]> wrote: >> >>> hi, I'm using ovs2.8 with dpdk-17052, and the '*NetXtreme II BCM57810 >>> 10 Gigabit Ethernet 168e*'. >>> There comes the error, while I try to bind the NIC using igb_uio. >>> >>> 2017-11-14T02:25:18.400Z|00362|dpdk|INFO|EAL: probe driver: 14e4:168e >>> net_bnx2x >>> 2017-11-14T02:25:18.400Z|00363|dpdk|ERR|EAL: Cannot open /dev/uio0: >>> Permission denied >>> >>> Then I chmod the file, like "chmod 777 /dev/uio0",(but I dont think this >>> is right way.) >>> but there comes other files with the same error, and I also chmod them. >>> And I do the actions: >>> chmod 777 /sys/bus/pci/devices/0000:20:00.1/* >>> chmod 777 /sys/class/uio/uio0/device/config >>> >>> Then , restart the ovs-dpdk, >>> But, there comes the following error: >>> 2017-11-14T02:40:05.436Z|8384580|dpdk|ERR|PMD: pci_read(): Can't read >>> from PCI config space >>> 2017-11-14T02:40:05.436Z|8384581|dpdk|ERR|PMD: pci_read(): Can't read >>> from PCI config space >>> 2017-11-14T02:40:05.436Z|8384582|dpdk|ERR|PMD: pci_read(): Can't read >>> from PCI config space >>> 2017-11-14T02:40:05.436Z|8384583|dpdk|ERR|PMD: pci_read(): Can't read >>> from PCI config space >>> 2017-11-14T02:40:05.436Z|8384584|dpdk|INFO|PMD: bnx2x_pci_get_caps(): >>> Failed to allocate memory >>> 2017-11-14T02:40:05.436Z|8384585|dpdk|INFO|PMD: bnx2x_attach(): PCIe >>> caps reading was failed >>> 2017-11-14T02:40:05.436Z|8384586|dpdk|ERR|PMD: bnx2x_common_dev_init(): >>> bnx2x_attach failed (-12) >>> 2017-11-14T02:40:05.436Z|8384587|dpdk|ERR|EAL: Requested device >>> 0000:20:00.1 cannot be used >>> >>> So, why there comes the Permission prolem? And what should I do for the >>> PCIe error? Or it is the NIC drivers' problem? >>> Thanks a lot. >>> >>> >>> _______________________________________________ >>> discuss mailing list >>> [email protected] >>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >>> >>> >> >
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
