It did not tell me anything: *Mar 20 11:42:23 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl add-port br0 dpdk-p0 -- set Interface dpdk-p0 type=dpdk options:dpdk-devargs=0000:00:0a.0* *Mar 20 11:42:23 ovs-vswitchd[23906]: ovs|00042|bridge|WARN|could not open network device dpdk-p0 (No such device)* *Mar 20 11:42:23 ovs-vswitchd[23906]: ovs|00044|bridge|WARN|could not open network device dpdk-p0 (No such device)*
A ./dpdk-devbind.py --status shows the below results, confirming device binding *Network devices using DPDK-compatible driver* *============================================* *0000:00:09.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio unused=i40e* *0000:00:0a.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio unused=i40e* *Network devices using kernel driver* *===================================* *0000:00:07.0 'XL710/X710 Virtual Function' if=ens7 drv=i40evf unused=igb_uio *Active** *Other network devices* *=====================* *<none>* *Crypto devices using DPDK-compatible driver* *===========================================* *<none>* *Crypto devices using kernel driver* *==================================* *<none>* *Other crypto devices* *====================* *<none>* But, I did notice a curious thing: when I init OVS with dpdk, using: ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem="1024,0" *2017-03-21T03:14:01Z|00007|dpdk|INFO|EAL ARGS: ovs-vswitchd --socket-mem 1024,0 -c 0x00000001* *EAL: Detected 5 lcore(s)* *EAL: Probing VFIO support...* *EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !* *EAL: PCI device 0000:00:07.0 on NUMA socket -1* *EAL: probe driver: 8086:154c net_i40e_vf* *EAL: PCI device 0000:00:09.0 on NUMA socket -1* *EAL: probe driver: 8086:1572 net_i40e* *PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.02 eetrack 80002284* *EAL: PCI device 0000:00:0a.0 on NUMA socket -1* *EAL: probe driver: 8086:1572 net_i40e* *PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.02 eetrack 80002284* I was wondering if the probe driver for 09.0 and 0a.0 should have been something like 'igb_uio'.. I am not sure if this is how it should be? Appreciate your inputs. Best Regards Advith Nagappa On Tue, Mar 21, 2017 at 3:33 AM, Ben Pfaff <b...@ovn.org> wrote: > On Tue, Mar 21, 2017 at 02:36:23AM +0100, Advith Nagappa wrote: > > Hi, > > > > I have DPDK 16.11.1 and OVS 2.6.1, with 1 Gb Huge page/ and 2 NICs bound > > with Igb_uio drivers. > > > > I run in to trouble while creating DPDK ports on the OVS bridge. > > > > > > *ovs-vsctl add-port br0 dpdk-p1 -- set Interface dpdk-p1 type=dpdk* > > > > works perfectly fine. > > > > But, > > > > *ovs-vsctl add-port br0 dpdk-p0 -- set Interface dpdk-p0 type=dpdk > > options:dpdk-devargs=0000:00:0a.0* > > > > gives an error: > > ovs-vsctl: Error detected while setting up 'dpdk-p0'. See ovs-vswitchd > log > > for details. > > What's in the log? >
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
