Hello Satish, On Tue, Oct 19, 2021 at 6:02 PM Ilya Maximets <i.maxim...@ovn.org> wrote: > > On 10/19/21 16:37, Satish Patel wrote: > > Thank you for reply, > > > > I figured out what my issue was. In ubuntu 20.04 you need to install > > libdpdk-dev package to install all librte drivers. after installing > > that package my issue got resolved and able to bind nic to ovs bridge. > > Hmm. Interesting. So, that's a really misleading error message from > a DPDK side. Thanks for sharing your solution! > > CC: David. FYI. > > Best regards, Ilya Maximets. > > > > > On Tue, Oct 19, 2021 at 9:46 AM Ilya Maximets <i.maxim...@ovn.org> wrote: > >> > >>> Update: > >>> > >>> After upgrade firmware still same errors > >>> > >>> # ethtool -i ext1 > >>> driver: ixgbe > >>> version: 5.1.0-k > >>> firmware-version: 0x800013d1, 20.0.16 > >>> expansion-rom-version: > >>> bus-info: 0000:af:00.1 > >>> supports-statistics: yes > >>> supports-test: yes > >>> supports-eeprom-access: yes > >>> supports-register-dump: yes > >>> supports-priv-flags: yes > >>> > >>> On Mon, Oct 4, 2021 at 9:33 AM Satish Patel <satish.txt at gmail.com> > >>> wrote: > >>>> > >>>> Folks, > >>>> > >>>> I am new to this nic series and just found a strange issue, i am sure > >>>> people are using this nic in production with dpdk. > >>>> > >>>> # ovs-vsctl add-port br-vlan dpdk-1 -- set Interface dpdk-1 type=dpdk > >>>> options:dpdk-devargs=0000:3b:00.1 > >>>> ovs-vsctl: Error detected while setting up 'dpdk-1': Error attaching > >>>> device '0000:3b:00.1' to DPDK. See ovs-vswitchd log for details. > >>>> ovs-vsctl: The default log directory is "/var/log/openvswitch". > >>>> > >>>> > >>>> 2021-10-04T13:20:05.751Z|00272|dpdk|ERR|EAL: Driver cannot attach the > >>>> device (0000:3b:00.1) > >>>> 2021-10-04T13:20:05.751Z|00273|dpdk|ERR|EAL: Failed to attach device > >>>> on primary process > >>>> 2021-10-04T13:20:05.751Z|00274|netdev_dpdk|WARN|Error attaching device > >>>> '0000:3b:00.1' to DPDK > >>>> 2021-10-04T13:20:05.751Z|00275|netdev|WARN|dpdk-1: could not set > >>>> configuration (Invalid argument) > >>>> 2021-10-04T13:20:05.751Z|00276|dpdk|ERR|Invalid port_id=32
- Something does seem strange but reading that installing libdpdk-dev solves your issue, it probably has to do with Ubuntu packaging. I suppose DPDK drivers are not in the dpdk package (which ovs depends on). I am not familiar with Ubuntu packaging, adding Christian and Luca in the loop. - About log messages above, what might be confusing for final users is that DPDK won't log a message when no driver is available. One reason it is done like this, is to avoid spamming messages for every pci devices on the system at PCI scan time. Maybe DPDK could do better and log a message when getting an explicit probe request on one pci device. > >> > >> Hi. The ERR log above likely means that you reached the maximum > >> number of DPDK ports. Most likely, your DPDK is built with default > >> max_ethports, which is 32, and your system has more devices. > >> You need to increase the value and re-build DPDK (and OVS afterwards), > >> or reduce the number of devices. This message about max_ethports is from OVS code. IIRC, it gets displayed when either DPDK probe fails or max number of port is reached. -- David Marchand _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
