Re: [ovs-discuss] Why testpmd fails to start in VM while l2fwd works in the same VM?

2016-08-26 Thread Charlie Li
Hi Mauricio, The issue is resolved by adding "--txqflags=0xf00 --disable-hw-vlan", that is, sudo -E ./testpmd -c 0x3 -n 2 -- -i --txqflags=0xf00 --disable-hw-vlan --portmask=0x3 --nb-cores=1 Thanks, Charlie On Fri, Aug 26, 2016 at 9:38 AM, Charlie Li wrote: > Thanks Mauricio, > > OVS - 2.5.0

[ovs-discuss] Is this a bug or specification??

2016-08-26 Thread Matsumoto Takuya
Hi . Im a Takuya. and a Japanese college student. so im not good at English. sry ;( ***first , please check this video https://youtu.be/0IVXS3CGUrI 0:00~0:30 create bridge( br0 ) 0:44 lose connection when delete flows.( Not exist flows ) 0:50~1:15 set protocol ( OpenFlow1.0 ) 1:15~1:55 s

Re: [ovs-discuss] Why testpmd fails to start in VM while l2fwd works in the same VM?

2016-08-26 Thread Charlie Li
Thanks Mauricio, OVS - 2.5.0 DPDK - 2.2.0 QEMU - 2.4.1 I used the ${DPDK_PATH}/tools/setup.sh to set up the environment including binding interfaces. after starting the setup.sh script, 1) select option 14 // build DPDK 2) select option 17 // st

Re: [ovs-discuss] Why testpmd fails to start in VM while l2fwd works in the same VM?

2016-08-26 Thread Mauricio Vasquez
Hello Charlie, On 08/25/2016 02:30 PM, Charlie Li wrote: Hi All, My host and VM both are running Fedora 23. In the host, DPDK (testpmd, l2fwd and l3fwd) works fine. Then I set up OVS with DPDK and pass two (dpdkvhostuser) ports to the VM. In the VM, l2fwd works fine, but testpmd fails to sta

Re: [ovs-discuss] Enable sFlow on br-tun cause OVS 2.5.0 crashed

2016-08-26 Thread Neil McKee
I think it would be OK to do this: tnlInProto = in_dsp ? dpif_sflow_tunnel_proto(in_dsp->tunnel_type) : 0; Neil -- Neil McKee InMon Corp. http://www.inmon.com On Fri, Aug 26, 2016 at 2:30 AM, 张东亚 wrote: > Hi List, > > Recently we are testing sFlow on OVS 2.5.0, since OVS decide whether d

[ovs-discuss] Enable sFlow on br-tun cause OVS 2.5.0 crashed

2016-08-26 Thread 张东亚
Hi List, Recently we are testing sFlow on OVS 2.5.0, since OVS decide whether do sample based on ingress bridge, we then enable sFlow on br-tun, and encounter following crash: #0 0x00434ca8 in dpif_sflow_received (ds=0x4266100, packet=packet@entry=0x7f3cb3fc8e18, flow=flow@entry=0x7f3cb3