Eugene, The only way that I found is roll-back to a Kernel version < 3.12. Today I did many tests with vanilla Kernel 3.11.10 and Canonical 3.11.0-24 I haven't anymore problem using datapath from OVS source. I’m using VXLAN so I can’t test OVS with kernel module because only from kernel 3.12 there is VXLAN tunnel support. At the beginning I said that I had the problem with kernel 3.11 and OVS datapath from source but this consideration come from a wrong analysis. ** My fault, sorry guys! ** >From my tests during the message “failed to put” I have packet loss.
Tomorrow I going to test the latest OVS LTS 2.0.1 with Kernel >=3.12 but I'm pretty sure that I will have the same problem. I let you know! Regards, Federico From: discuss [discuss-boun...@openvswitch.org] on behalf of Eugene Istomin [e.isto...@edss.ee] Sent: Thursday, June 26, 2014 8:46 PM To: Jesse Gross Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] failed to put[create][modify] Jesse, our syslog rules covers all possible syslog-like logs (including kernel), i don't find any related messages (dmesg are clean too). --- Best regards, Eugene Istomin EDS Systems e.isto...@edss.ee Work: +372-6409-600 On Thursday, June 26, 2014 11:39:33 AM Jesse Gross wrote: > On Thu, Jun 26, 2014 at 11:33 AM, Eugene Istomin <e.isto...@edss.ee> wrote: > > After implementing log parsing on some servers we discover the same issue > > (mac are masked): > > > > > > > > <28>Jun 26 20:57:08 ovs-vswitchd: > > ovs|207944|dpif(handler_1)|WARN|system@ovs-system: failed to > > put[create][modify] (Invalid argument) > > skb_priority(0),in_port(2),skb_mark(0/0),eth(src=XX,dst=ff:ff:ff:ff:ff:ff) > > ,eth_type(0x8100),vlan(vid=32/0x0,pcp=0/0x0,cfi= > > > > 1/0),encap(eth_type(0x0800),ipv4(src=10.0.89.165/0.0.0.0,dst=10.0.89.255/0 > > .0.0.0,proto=17/0,tos=0/0,ttl=128/0,frag=no/0xff),udp(src=137/0,dst=137/0) > > ), actions:drop > > > > > > > > 28>Jun 26 21:01:56 ovs-vswitchd: > > ovs|207962|dpif(handler_1)|WARN|system@ovs-system: failed to > > put[create][modify] (Invalid argument) > > skb_priority(0),in_port(2),skb_mark(0/0),eth(src=XX,dst=XX),eth_type(0x810 > > 0),vlan(vid=217/0x0,pcp=0/0x0,cfi > > > > =1/0),encap(eth_type(0x0800),ipv4(src=0.0.0.0/0.0.0.0,dst=224.0.0.1/0.0.0. > > 0,proto=2/0,tos=0xc0/0,ttl=1/0,frag=no/0xff)), actions:drop > > > > > > > > <28>Jun 26 21:14:00 ovs-vswitchd: > > ovs|208000|dpif(handler_1)|WARN|system@ovs-system: failed to > > put[create][modify] (Invalid argument) > > skb_priority(0),in_port(2),skb_mark(0/0),eth(src=XX,dst=XX),eth_type(0x810 > > 0),vlan(vid=1000,pcp=0),encap(eth_type(0x0800), > > > > ipv4(src=10.100.103.153/0.0.0.0,dst=10.100.103.114/255.255.255.255,proto=6 > > /0,tos=0/0,ttl=64/0,frag=no/0xff),tcp(src=7701/0,dst=24291/0)), > > actions:pop_vlan,5 > > > > > > > > > > > > Kernel 3.12.18, OVS 2.1.2, in-kernel ovs module, xen 4.4. > > > > We will update kernels & xen next week in order not to reflect already > > resolved problems. > > Do you have any messages in dmesg? > > > By the way, there are some xen-related network issues in VMs like "xennet: > > skb rides the rocket: 19 slots" leads to packet loss/retransmitting in > > network-sensitive applications (like VM-to-VM DRBD). This may be xen > > netback/netfront bugs. > > Yes, this is from Xen. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
