Re: [ovs-discuss] Failed to build Open vSwitch Kernel Modules on CentOS 7 (kernel 3.10.0-514.2.2.el7.x86_64)

Great, that patch works for me. After cherry-picked that patch to 2.6.1, we can also build the 2.6.1 ovs kmod. Thank you very much. On Thu, Jan 12, 2017 at 10:21 AM, Joe Stringer wrote: > Does your master include this commit? > >

Re: [ovs-discuss] Failed to build Open vSwitch Kernel Modules on CentOS 7 (kernel 3.10.0-514.2.2.el7.x86_64)

On Wed, Jan 11, 2017 at 03:03:45PM -0800, Joe Stringer wrote: > On 9 January 2017 at 19:01, liu yulong wrote: > > Hi experts, > > > > We have failed to build Open vSwitch Kernel Modules on CentOS 7 (kernel > > 3.10.0-514.2.2.el7.x86_64). > > > > Here are some traces we

Re: [ovs-discuss] Failed to build Open vSwitch Kernel Modules on CentOS 7 (kernel 3.10.0-514.2.2.el7.x86_64)

On 9 January 2017 at 19:01, liu yulong wrote: > Hi experts, > > We have failed to build Open vSwitch Kernel Modules on CentOS 7 (kernel > 3.10.0-514.2.2.el7.x86_64). > > Here are some traces we got: > http://paste.openstack.org/show/594350/ > > Steps: > 1. download the

Re: [ovs-discuss] clear interface statistics

On Wed, Jan 11, 2017 at 09:48:47AM +, Avi Cohen wrote: > Is it possible to clear interface stats ? No. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] Failed to build Open vSwitch Kernel Modules on CentOS 7 (kernel 3.10.0-514.2.2.el7.x86_64)

Hi experts, We have failed to build Open vSwitch Kernel Modules on CentOS 7 (kernel 3.10.0-514.2.2.el7.x86_64). Here are some traces we got: http://paste.openstack.org/show/594350/ Steps: 1. download the current openvswitch release: http://openvswitch.org/releases/openvswitch-2.6.1.tar.gz 2.

[ovs-discuss] how many queues in openvswitch?

Dear friend: hello,I am a graduated student in BJTU, China, my major is CS. I'm interested in openvswitch, and i have a question. Could you tell me how many queues or buffer are there in openvswitch , and what they are? I'm looking forward to your reply. Thanks! Sincerely yours,

Re: [ovs-discuss] Re： On OVNDB-HA using pacemaker two issues discussed

When /etc/openvswitch/ovn-northd-db-params.conf is present in the machine(s) that northd is starting, northd service will not launch the ovsdb servers. You can have a look at https://review.openstack.org/#/c/372274/3/manifests/profile/pacemaker/neutron/plugins/ml2/ovn.pp to know how its done

Re: [ovs-discuss] On OVNDB-HA using pacemaker two issues discussed

On Wednesday 07 December 2016 08:58 AM, 姜尚0387 wrote: I am learning OVNDB-HA using pacemaker, I feel this is a good design. At the same time I have two questions and would like to discuss: 1, we have two resources, one is the master node of the OVNDB, one is VIP. Pacemaker

Re: [ovs-discuss] kernel panic when setting QoS parameters more than once

On 10 January 2017 at 05:46, Riccardo R. wrote: > Hi, > > By setting QoS parameters more than once on an OpenvSwitch bridge, we caused > kernel panic on our machine. This is > reproducible with the following commands: > > $ ovs-vsctl add-br mybridge > $ ovs-vsctl

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

On 01/11/2017 03:54 AM, Shravan S K wrote: > Like this? > vm01---| > > |--vm03 > >

Re: [ovs-discuss] ovs-bonded igb nics flopping

On Wed, Jan 11, 2017 at 01:15:10PM +, Matias Vara wrote: > Hi everyone and sorry for the multiple emails, we are facing a flopping of > igb (5.3.4.4) nics which are bonded by using openvswitch. I am in XenServer > which is based on CentOS. I am not sure if the problem is the driver or >

[ovs-discuss] ovs-bonded igb nics flopping

Hi everyone and sorry for the multiple emails, we are facing a flopping of igb (5.3.4.4) nics which are bonded by using openvswitch. I am in XenServer which is based on CentOS. I am not sure if the problem is the driver or openvswitch. We have six nics that are bonded into two groups of three. The

Re: [ovs-discuss] VXLAN support in OVS 2.5.0

Like this? vm01---| |--vm03 br1(vxlanport1)br-int1=br-int2--(vxlanport2)br2 vm02---| |---vm04 What is the need for the bridges br-int1 and br-int2? Why is it not possible without them(as the

[ovs-discuss] netdev_linux_update_flags() needs seq_change() ?

Hi, After all statements of netdev_linux_update_flags() executed successfully, it also executes seq_change() to tell ofproto_run() something changed to update ovsdb. And in order to config port to linkup can update ovsdb. it needs to use "a->config == b->config" instead of "&& !((a->config ^