Thanks Ben and Alon for your help. I want to share the solution in case someone else hits the same issue: dpdkvhostuser type requires the bridge to be created with datatype_path=netdev as stated in the documentation: http://docs.openvswitch.org/en/latest/howto/dpdk/
Regards, Nicolas Vazquez El jue., 11 de julio de 2019 17:39, Ben Pfaff <[email protected]> escribió: > I forgot to finish my thought. > > For the most recent version of OVS, if DPDK is supported, so is > dpdkvhostuser (and dpdkvhostuserclient, which is not deprecated). Maybe > dpdkvhostuser was optional in 2.9. > > On Thu, Jul 11, 2019 at 01:22:20PM -0700, Ben Pfaff wrote: > > It looks like dpdkvhostuser ports are deprecated, although they should > > still work. > > > > On Thu, Jul 11, 2019 at 12:35:53AM -0300, Nicolas Vazquez wrote: > > > My mistake :) > > > > > > Been checking the /var/run/openvswitch/ovs-vswitchd.log and found this > is > > > the error: > > > > > > 2019-07-11T03:11:31.789Z|00226|netdev_dpdk|INFO|Socket > > > /var/run/openvswitch/test created for vhost-user port test > > > 2019-07-11T03:11:31.790Z|00227|dpif_netlink|WARN|system@ovs-system: > cannot > > > create port `test' because it has unsupported type `dpdkvhostuser' > > > > > > I thought maybe DPDK was not being initialized properly but > surprisingly > > > noticed these earlier in the logs: > > > > > > 2019-07-10T18:56:02.183Z|00039|dpdk|INFO|DPDK Enabled - initializing... > > > 2019-07-10T18:56:02.183Z|00040|dpdk|INFO|No vhost-sock-dir provided - > > > defaulting to /var/run/openvswitch > > > 2019-07-10T18:56:02.183Z|00041|dpdk|INFO|EAL ARGS: ovs-vswitchd > > > --socket-mem 1024,0 -c 0x00000001 > > > 2019-07-10T18:56:03.846Z|00042|dpdk|INFO|DPDK pdump packet capture > enabled > > > 2019-07-10T18:56:03.851Z|00043|dpdk|INFO|DPDK Enabled - initialized > > > > > > El mié., 10 jul. 2019 a las 16:38, Ben Pfaff (<[email protected]>) escribió: > > > > > > > On Wed, Jul 10, 2019 at 04:16:14PM -0300, Nicolas Vazquez wrote: > > > > > Thank you both. > > > > > > > > > > I tried replacing the OVS packages. Have bind NIC to DPDK support: > > > > > # dpdk-devbind --status > > > > > > > > > > Network devices using DPDK-compatible driver > > > > > ============================================ > > > > > 0000:02:04.0 '82545EM Gigabit Ethernet Controller (Copper) 100f' > > > > > drv=igb_uio unused= > > > > > > > > > > However whenever I try to add a DPDK vHost user port it fails: > > > > > # ovs-vsctl add-port cloudbr0 test -- set Interface test > > > > type=dpdkvhostuser > > > > > ovs-vsctl: Error detected while setting up 'test': could not add > network > > > > > device test to ofproto (Invalid argument). See ovs-vswitchd log > for > > > > > details. > > > > > ovs-vsctl: The default log directory is "/var/log/openvswitch". > > > > > > > > Did you look in the log? > > > > > > > > The above does *not* mean to run "ovs-vswitchd log", which is not > going > > > > to be helpful. > > > > > > > > > # ovs-vswitchd log > > > > > 2019-07-10T19:11:29Z|00001|ovs_numa|INFO|Discovered 3 CPU cores on > NUMA > > > > > node 0 > > > > > 2019-07-10T19:11:29Z|00002|ovs_numa|INFO|Discovered 1 NUMA nodes > and 3 > > > > CPU > > > > > cores > > > > > 2019-07-10T19:11:29Z|00003|reconnect|INFO|log: connecting... > > > > > 2019-07-10T19:11:29Z|00004|reconnect|INFO|log: connection attempt > failed > > > > > (Address family not supported by protocol) > > > > > 2019-07-10T19:11:29Z|00005|reconnect|INFO|log: waiting 1 seconds > before > > > > > reconnect > > > > > 2019-07-10T19:11:30Z|00006|reconnect|INFO|log: connecting... > > > > > 2019-07-10T19:11:30Z|00007|reconnect|INFO|log: connection attempt > failed > > > > > (Address family not supported by protocol) > > > > > 2019-07-10T19:11:30Z|00008|reconnect|INFO|log: waiting 2 seconds > before > > > > > reconnect > > > > > > > > >
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
