Hi, check my former link - as it said you should check the syslog/journal around the time when starting the dpdk enabled openvswitch. At that time the device probing and initialization takes place, and there you likely find why you have no dpdk0 Probably something around the iommu as this is often the case with vfio-pci.
Kind Regards, Christian Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd On Thu, Jul 7, 2016 at 11:04 AM, shyam yeduru <yedurush...@hotmail.com> wrote: > Hi , > > Sorry for confusing you. I will explain my issue clearly. > > We have installed OVS and DPDK on Ubuntu14.04. We have done our > configuration using Physical NIC and Virtual > Functions (SR-IOV produced Interfaces). > > We have followed this link: > https://software.intel.com/en-us/articles/using-open-vswitch-with-dpdk-for-inter-vm-nfv-applications > > We are unable to add dpdk on top of OVS bridge. > > Server configurations : > root@kvmsriov:~# cat /proc/cmdline > BOOT_IMAGE=/vmlinuz-4.4.0-28-generic root=/dev/mapper/kvmsriov--vg-root ro > intel_iommu=on > > root@kvmsriov:~# grep Huge /proc/meminfo > AnonHugePages: 5595136 kB > HugePages_Total: 256 > HugePages_Free: 256 > HugePages_Rsvd: 0 > HugePages_Surp: 0 > Hugepagesize: 2048 kB > root@kvmsriov:~# > > root@kvmsriov:~# dpdks -s > Network devices using DPDK-compatible driver > ============================================ > 0000:07:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=vfio-pci > unused=ixgbe > 0000:07:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=vfio-pci > unused=ixgbe > 0000:07:10.0 '82599 Ethernet Controller Virtual Function' drv=vfio-pci > unused=ixgbevf > 0000:07:10.1 '82599 Ethernet Controller Virtual Function' drv=vfio-pci > unused=ixgbevf > Network devices using kernel driver > =================================== > 0000:03:00.0 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eno1 drv=tg3 > unused=vfio-pci *Active* > 0000:03:00.1 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eno2 drv=tg3 > unused=vfio-pci > 0000:03:00.2 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eno3 drv=tg3 > unused=vfio-pci > 0000:03:00.3 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eno4 drv=tg3 > unused=vfio-pci > Other network devices > ===================== > <none> > > OVS > root@kvmsriov:~# ovs-vsctl show > 910cdc54-e27f-4f5b-ae01-d180df6973ec > Bridge "br0" > Port "vhost-user1" > Interface "vhost-user1" > type: dpdkvhostuser > error: "could not open network device vhost-user1 > (Address family not supported by protocol)" > Port "dpdk0" > Interface "dpdk0" > type: dpdk > error: "could not open network device dpdk0 (Address > family not supported by protocol)" > Port "br0" > Interface "br0" > type: internal > Bridge "ovsbr0" > Port "vnet1" > Interface "vnet1" > Port "ovsbr0" > Interface "ovsbr0" > type: internal > Port "vnet2" > Interface "vnet2" > ovs_version: "2.5.0" > root@kvmsriov:~# > > Enclosed the logs of the server here with. Please do the needful. > root@kvmsriov:~# tailf /var/log/openvswitch/ovs-vswitchd.log > 2016-07-07T14:55:08.311Z|00091|bridge|INFO|bridge br0: using datapath ID > 0000e21cf47fa440 > 2016-07-07T14:55:08.311Z|00092|connmgr|INFO|br0: added service controller > "punix:/var/run/openvswitch/br0.mgmt" > 2016-07-07T14:55:13.488Z|00093|memory|INFO|peak resident set size grew 93% > in last 600282.6 seconds, from 117000 kB to 225472 kB > 2016-07-07T14:55:13.488Z|00094|memory|INFO|handlers:16 ports:4 > revalidators:8 rules:10 > 2016-07-07T14:55:19.411Z|00095|netdev|WARN|could not create netdev dpdk0 > of unknown type dpdk > 2016-07-07T14:55:19.411Z|00096|bridge|WARN|could not open network device > dpdk0 (Address family not supported by protocol) > 2016-07-07T14:55:37.723Z|00097|netdev|WARN|could not create netdev > vhost-user1 of unknown type dpdkvhostuser > 2016-07-07T14:55:37.723Z|00098|bridge|WARN|could not open network device > vhost-user1 (Address family not supported by protocol) > 2016-07-07T14:55:37.723Z|00099|netdev|WARN|could not create netdev dpdk0 > of unknown type dpdk > 2016-07-07T14:55:37.723Z|00100|bridge|WARN|could not open network device > dpdk0 (Address family not supported by protocol) > > Please advise.... > > Thanks > Shyam Yeduru > > > > ------------------------------ > From: christian.ehrha...@canonical.com > Date: Thu, 7 Jul 2016 08:12:10 +0200 > > Subject: Re: [ovs-discuss] OVS+DPDK issue on Ubuntu 16.04 > To: yedurush...@hotmail.com > CC: discuss@openvswitch.org > > Hi, > I beg a pardon but I'm not entirely clear what you mean with "... mount > the Intel 10gig ..." > Anyway what I've seen most often is that people struggle with some core > parts of the setup and then get refused by OVS trying to add the DPDK port. > What you report "...we are not able to add dpdk0 port to ovs bridge..." > sounds very similar. > > In the past all questions I got only needed to check logs, identify the > issue in base ovs+dpdk setup and then things started to work for them. > Please take a look at > http://askubuntu.com/questions/786510/using-openvswitch-with-dpdk-in-ubuntu-16-04/789203#789203 > > If it helps you please give it an upvote and let me know. > I might consider adding this as a troubleshooting section to the > serverguide if this really is a common case. > > Kind Regards, > Christian > > Christian Ehrhardt > Software Engineer, Ubuntu Server > Canonical Ltd > > On Thu, Jul 7, 2016 at 6:54 AM, shyam yeduru <yedurush...@hotmail.com> > wrote: > > Hi Christian, > > Thanks for writing us. We are able to mount the Intel 10gig DPDK Supported > NIC Cards as stated in below url. > Our Test Cases: > 1.0 Intel 10gig with Pass Through on to Vyatta Router , Traffic Generator > was IXIA (No DPDK Enabled Interfaces) > 2.0 Intel 10gig with Pass Through on to Vyatta Router , Traffic Generator > was IXIA ( DPDK Enabled Interfaces) > 3.0 OVS Bridge Interfaces on to Vyatta Router, Traffic Generator was IXIA > (No DPDK ) > 4.0 OVS Bridge Interfaces on to Vyatta Router, Traffic Generator was IXIA > (DPDK) > > From the above 4 scenarios, we are not able to add dpdk0 port to ovs > bridge (4 Test Cases). > > OVS+DPDK > > http://openvswitch.org/support/dist-docs/INSTALL.DPDK.md.txt > > > Pls advise, how to add the ovs along with dpdk . > > Thanks > Shyam yeduru > ------------------------------ > From: christian.ehrha...@canonical.com > Date: Tue, 5 Jul 2016 18:32:15 +0200 > Subject: Re: [ovs-discuss] OVS+DPDK issue on Ubuntu 16.04 > To: yedurush...@hotmail.com > CC: discuss@openvswitch.org; sy00454...@techmahindra.com > > > Hi, > The TL;DR is that in Ubuntu 16.04 the base openvswitch-switch package > knows nothing about dpdk. > But the openvswitch-switch-dpdk package does. > > please follow the whole page around > https://help.ubuntu.com/16.04/serverguide/DPDK.html#dpdk-openvswitch for > some guidance. > > > > Christian Ehrhardt > Software Engineer, Ubuntu Server > Canonical Ltd > > On Mon, Jul 4, 2016 at 9:51 AM, shyam yeduru <yedurush...@hotmail.com> > wrote: > > Hi Team, > > We have used ovs+dpdk installed and trying to test with Brocade Vyatta VNF > which is DPDK Supported. We were not able to add dpdk0 port to OVS Bridge. > > Error log : > > 2016-06-16T19:28:29.819Z|00021|bridge|INFO|bridge ovsbr0: added interface > ovsbr0 on port 65534 > 2016-06-16T19:28:29.819Z|00022|bridge|INFO|bridge ovsbr0: added interface > vnet0 on port 2 > 2016-06-16T19:28:29.819Z|00023|bridge|INFO|bridge ovsbr0: added interface > enp7s16f4 on port 1 > 2016-06-16T19:28:29.819Z|00024|netdev|WARN|could not create netdev dpdk0 > of unknown type dpdk > 2016-06-16T19:28:29.819Z|00025|bridge|WARN|could not open network device > dpdk0 (Address family not supported by protocol) > 2016-06-16T19:28:29.819Z|00026|bridge|INFO|bridge ovsbr1: added interface > ovsbr1 on port 65534 > 2016-06-16T19:28:29.819Z|00027|netdev|WARN|could not create netdev > vhost-user1 of unknown type dpdkvhostuser > 2016-06-16T19:28:29.819Z|00028|bridge|WARN|could not open network device > vhost-user1 (Address family not supported by protocol) > 2016-06-16T19:28:29.819Z|00029|bridge|INFO|bridge ovsbr0: using datapath > ID 0000c67be1a7aa45 > 2016-06-16T19:28:29.820Z|00030|connmgr|INFO|ovsbr0: added service > controller "punix:/var/run/openvswitch/ovsbr0.mgmt" > 2016-06-16T19:28:29.856Z|00031|bridge|INFO|bridge ovsbr1: using datapath > ID 0000821322a5cb42 > 2016-06-16T19:28:29.856Z|00032|connmgr|INFO|ovsbr1: added service > controller "punix:/var/run/openvswitch/ovsbr1.mgmt" > 2016-06-16T19:28:29.894Z|00033|netdev|WARN|could not create netdev dpdk0 > of unknown type dpdk > 2016-06-16T19:28:29.894Z|00034|bridge|WARN|could not open network device > dpdk0 (Address family not supported by protocol) > 2016-06-16T19:28:29.894Z|00035|netdev|WARN|could not create netdev > vhost-user1 of unknown type dpdkvhostuser > 2016-06-16T19:28:29.894Z|00036|bridge|WARN|could not open network device > vhost-user1 (Address family not supported by protocol) > 2016-06-16T19:28:29.896Z|00037|bridge|INFO|ovs-vswitchd (Open vSwitch) > 2.5.0 > > Operating System : Ubuntu 16.04 > Hardward : > Manufacturer: HP > Product Name: ProLiant DL380p Gen8 > Intel 10gig DPDK Support with Intel SFP’s > OpenvSwitch : > Architecture: amd64 > Source: openvswitch > Version: 2.5.0-0ubuntu1 > Depends: kmod | module-init-tools, netbase, openvswitch-common (= > 2.5.0-0ubuntu1), procps, python-argparse, uuid-runtime, init-system-helpers > (>= 1.18~), lsb-base (>= 4.1+Debian11ubuntu7), python:any, libc6 (>= 2.14), > libcap-ng0, libssl1.0.0 (>= 1.0.0) > Filename: > pool/main/o/openvswitch/openvswitch-switch_2.5.0-0ubuntu1_amd64.deb > > OVS+DPDK > Architecture: amd64 > Source: openvswitch > Version: 2.5.0-0ubuntu1 > Depends: dpdk, openvswitch-switch (= 2.5.0-0ubuntu1), libc6 (>= 2.14), > libcap-ng0, libdpdk0 (>= 2.2), libssl1.0.0 (>= 1.0.0) > Filename: > pool/main/o/openvswitch/openvswitch-switch-dpdk_2.5.0-0ubuntu1_amd64.deb > > Please advise, how do we proceed further and achieve configurations. > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss > > > >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
