Thank you for your reply.
I could find the answer while tracking existence of ifcfg files!
The cause was execution order of inserting ovs kernel module starting and
ovs-db/daemon. I inserted ovs-module after starting ovs-db/daemon. There
were some warning and error messages for this at starting o
Just check that you have scripts there for the bridges at
/etc/sysconfig/network-scripts/ifcfg-br0 & ifcfg-br1
From: discuss-boun...@openvswitch.org [mailto:discuss-boun...@openvswitch.org]
On Behalf Of JinHwan Hwang
Sent: Thursday, May 30, 2013 6:11 AM
To: discuss@openvswitch.org
Subject: [ovs-
Thank you for providing the requested information.
I found that "subfacet->slow_path_reason == 0" indicates packets is processed
by fast path, so in this case the packet is directly forwarded by the kernel.
If it is in slow-path such as "slow_controller", the packets will all be
forwarded to us
(English is not my first language. Sorry for my poor English )
OS :
Linux nc233 2.6.32-220.17.1.el6.x86_64 #1 SMP Tue May 15 17:16:46 CDT 2012
x86_64 x86_64 x86_64 GNU/Linux
CentOS release 6.3 (Final)
open vswitch : 1.11.90
I installed the ovs by using source install. At that time it worked
prope
On Tue, May 28, 2013 at 11:38 AM, zuo wrote:
> Hi,
> Recently I read the code of OpenvSwitch (version 1.9) to learn how packet is
> processed in datapath and userspace. However, there are some issues that I
> didn’t understand clearly. Can anybody help me?
> (1)When the first packet of a flo
On Wed, May 29, 2013 at 11:29 PM, Padmanabhan Krishnan wrote:
> Thanks for the reply. Sure, i can submit a patch sometime next week.
Ben already wrote one and you were CC'ed:
http://openvswitch.org/pipermail/dev/2013-May/027811.html
> I am learning the code, so didn't know which one has more pre
Linux bonds don't pass vlan information through to the driver. If you
use OVS bonding then you shouldn't have this problem.
On Wed, May 29, 2013 at 11:08 AM, Kris zhang wrote:
> I found the reason, the problem is not caused by vlan splinters, it caused
> by bond0. I don't know why, but if remove
Every release has improved performance, so I'd recommend the latest (1.10.x).
If you want the long-term support version, then 1.9.x. hping is a particularly
difficult use-case, since it sets up lots of different short-lived flows
instead of sending lots of packets through just a few flows. Th
Thanks for the reply. Sure, i can submit a patch sometime next week.
I am learning the code, so didn't know which one has more precedence. Looking
at:
http://openvswitch.org/pipermail/git/2011-August/001692.html
I was of the opinion that flows cannot be installed for special Mcast packets
(lik
On Wed, May 29, 2013 at 11:39:07AM +0200, Alessandra Agosta wrote:
> How can I update my openvswitch? Should I remove my version or do an update of
> what I have? Moreover, among the versions there is one recommended?
Just follow the instructions in INSTALL. Version 1.9 is probably a good
choice.
Hi Justin,
Which version do u recommend,which is capable enough to use
low cpu:
I tested on kvm *host1* running *OVS 1.6.90* and created vm-1 and on
another kvm *host2* created 2 vms (vm1 and vm2) then from vm2 and vm3
using hping3 i flooded vm1.
initially flow was 500 later came
How can I update my openvswitch? Should I remove my version or do an update of
what I have? Moreover, among the versions there is one recommended?
Thank you very much
--
Alessandra
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/m
12 matches
Mail list logo
