Re: [ovs-discuss] Open V Switch module

2024-05-03 Thread Flavio Leitner via discuss
On Fri, 3 May 2024 17:45:42 -0700 Abu Rasheda via discuss wrote: > Since the OVS kernel code has moved to the Linux kernel tree since the > 3.0 release. I did not find the module in /lib/module on Redhat 9.3, > but I did find it in > >

Re: [ovs-discuss] Urgent Help needed: OVS 3.2.2 Strange TC DROPs

2024-04-17 Thread Flavio Leitner via discuss
On Wed, 17 Apr 2024 12:26:27 -0700 Gavin McKee wrote: > Hi Flavio, > > I had to restart the Open vSwitch across 16 machines to resolve the > issue for a customer . I think it will occur again and when it does > I'll use that command to gather the tc information. > > Until then I think I have

Re: [ovs-discuss] Urgent Help needed: OVS 3.2.2 Strange TC DROPs

2024-04-17 Thread Flavio Leitner via discuss
Hi Gavin, It would be helpful if you can provide some TC dumps from the "good" state to the "bad" state to see how it was and what changes. Something like: # tc -s filter show dev enp148s0f0_1 ingress I haven't checked the attached files, but one suggestion is to check if this is not a

Re: [ovs-discuss] OVS with or without DPDK Throughput issue

2024-02-02 Thread Flavio Leitner via discuss
On Wed, 31 Jan 2024 17:45:30 -0800 MIchael Miller via discuss wrote: > Hi All, > >  Not sure if this is the right forum for this question but figured I > would start here. > >  Have implemented several dedicated kvm based private virtualization > server in several Outside Data Center (have

Re: [ovs-discuss] VxLAN in Userspace

2019-06-19 Thread Flavio Leitner via discuss
On Tue, Jun 18, 2019 at 03:12:51PM -0400, Vasu Dasari wrote: > On Tue, Jun 18, 2019 at 12:21 PM Flavio Leitner wrote: > > > On Tue, Jun 18, 2019 at 10:41:16AM -0400, Vasu Dasari wrote: > > > Flavio, > > > > > > The device(could be a regular interface) should have been added to OVS > > with > > >

Re: [ovs-discuss] VxLAN in Userspace

2019-06-18 Thread Flavio Leitner via discuss
On Tue, Jun 18, 2019 at 10:41:16AM -0400, Vasu Dasari wrote: > Flavio, > > The device(could be a regular interface) should have been added to OVS with > "add-port" and when it is removed, ARP entries learnt on it well be removed > as well. Not necessarily. You could have a regular kernel

Re: [ovs-discuss] VxLAN in Userspace

2019-06-14 Thread Flavio Leitner via discuss
On Thu, Jun 13, 2019 at 10:58:21PM -0400, Vasu Dasari wrote: > Flavio, > > tnl_neigh_cache_flush(), flushes entire tunnel ARP table. When a bridge is > removed, ARP entries learnt on that bridge alone have to be removed. > Entries from other bridges have to be in tact. > > I am thinking of doing

Re: [ovs-discuss] VxLAN in Userspace

2019-06-13 Thread Flavio Leitner via discuss
On Wed, Jun 12, 2019 at 07:18:27PM -0400, Vasu Dasari wrote: > Thanks Ben. Meanwhile I think I found an bug in OVS 2.9.0 with stale ARP > entries after a bridge is deleted. > > I ran my tunneling experiment successfully. Used mininet to simulate the > environment. After quitting the mininet,

Re: [ovs-discuss] losing packets when vxlan port is used

2019-06-12 Thread Flavio Leitner via discuss
On Wed, Jun 12, 2019 at 02:10:19PM +0200, Miroslav Kubiczek wrote: > Hello, > > I'm experiencing packets loss on OpenvSwitch host during transmission to > vxlan port under higher traffic load. > > Some statistics from 2 machines are here (30 seconds run): > > 10.10.12.148-ens224-TX 625 100

Re: [ovs-discuss] Restarting network kills ovs-vswitchd (and network)... ?

2019-05-17 Thread Flavio Leitner via discuss
On Fri, May 17, 2019 at 09:45:36AM +, SCHAER Frederic wrote: > Hi > > Thank you for your answer. > I actually forgot to say I already had checked the syslogs, the ovs and the > network journals/logs... no coredump reference anywhere > > For me a core dump or a crash would not return an exit

Re: [ovs-discuss] OVS - QEMU unable to create vhostuserclient socket at /var/run/openvswitch

2019-05-17 Thread Flavio Leitner via discuss
On Fri, May 17, 2019 at 06:39:26AM -0300, Flavio Leitner via discuss wrote: > On Fri, May 17, 2019 at 09:13:08AM +, Joan Vidal wrote: > > Hi Flavio, > > > > SELinux is disabled. > > Could you add the port to OVS and tell us the file ownership > and perms of the

Re: [ovs-discuss] OVS - QEMU unable to create vhostuserclient socket at /var/run/openvswitch

2019-05-17 Thread Flavio Leitner via discuss
On Fri, May 17, 2019 at 09:13:08AM +, Joan Vidal wrote: > Hi Flavio, > > SELinux is disabled. Could you add the port to OVS and tell us the file ownership and perms of the socket? (/var/run/openvswitch/vhost0) The same for /var/run/openvswitch directory. One quick test is to use /tmp

Re: [ovs-discuss] OVS - QEMU unable to create vhostuserclient socket at /var/run/openvswitch

2019-05-17 Thread Flavio Leitner via discuss
Do you have SELinux enabled? Sounds like the policies are not updated. fbl On Thu, May 16, 2019 at 04:16:04PM +, Joan Vidal wrote: > Hi Ian, > > Upgraded QEMU version to 2.10.0(qemu-kvm-ev-2.10.0-21.el7_5.7.1) > Changed /etc/libvirt/qemu.conf > user = "root" > group = "root" > > And

Re: [ovs-discuss] Restarting network kills ovs-vswitchd (and network)... ?

2019-05-17 Thread Flavio Leitner via discuss
On Thu, May 16, 2019 at 09:34:28AM +, SCHAER Frederic wrote: > Hi, > I'm facing an issue with openvswitch, which I think is new (not even sure). > here is the description : > > * What you did that make the problem appear. > > I am configuring openstack (compute, network) nodes using OVS

Re: [ovs-discuss] ovs-vswitchd port limit with OpenStack

2019-05-02 Thread Flavio Leitner via discuss
On Thu, May 02, 2019 at 04:44:42PM -0300, Flavio Leitner via discuss wrote: > On Tue, Apr 30, 2019 at 04:50:48PM -0700, Ben Pfaff wrote: > > On Fri, Apr 26, 2019 at 11:52:22AM -0500, William Konitzer wrote: > > > I'm reading > > > (http://www.openvswitch.org/support/d

Re: [ovs-discuss] ovs-vswitchd port limit with OpenStack

2019-05-02 Thread Flavio Leitner via discuss
On Tue, Apr 30, 2019 at 04:50:48PM -0700, Ben Pfaff wrote: > On Fri, Apr 26, 2019 at 11:52:22AM -0500, William Konitzer wrote: > > I'm reading > > (http://www.openvswitch.org/support/dist-docs/ovs-vswitchd.8.txt > > section LIMITS) and it says "Performance will degrade beyond 1,024 > > ports per