Hey Rahul,
The warning means the handler threads was busying running for 16 seconds
before calling time_poll() again (in other words, before trying to sleep
again).
The log showed suspiciously long system running. Definitely not expected,
Could you confirm the ovs kernel module version via 'mod
These logs are coming from *lib/timeval.c *under the function
*log_poll_interval* in OVS source code.
On Wed, Dec 10, 2014 at 12:17 PM, Rahul Arora
wrote:
> Alex,
>
> I am getting these logs when i am getting 100% CPU usage.
>
> Please have a look on the RED part.
>
> ==
Alex,
I am getting these logs when i am getting 100% CPU usage.
Please have a look on the RED part.
==
2014-11-25T06:04:37.604Z|00095|timeval(handler5)|WARN|Unreasonably long
16127ms poll interval (260ms user, 17320ms system)
2014-11-25T06:04:37.604Z|00096|tim
I believe it has 16 cores, with hyperthreading disabled,
On Tue, Dec 9, 2014 at 9:37 PM, Rahul Arora
wrote:
> Hi Alex,
>
> The platform which you are using for your performance testing is of how
> many cores??
>
> On Tue, Dec 9, 2014 at 10:45 PM, Alex Wang wrote:
>
>> Hey Rahul,
>>
>> The kerne
Hi Alex,
The platform which you are using for your performance testing is of how
many cores??
On Tue, Dec 9, 2014 at 10:45 PM, Alex Wang wrote:
> Hey Rahul,
>
> The kernel version should not make a difference,
>
> I'm curious, since ovs-2.3.0 is multithreaded, not sure how do you measure
> the
On 12/8/14, 2:02 AM, Justin Pettit wrote:
On Dec 7, 2014, at 5:44 PM, Mark Haywood wrote:
The FAQ says that there are usually several long-term support releases a year.
What determines when an LTS is released and when would there be another one
taking the place of 2.3.0?
The LTS releases hap
As others might have noticed by now my loopback interface was not correctly
configured to come up automatically since in my auto directive I specify
"lo0" but the interface is actually only named "lo". Missing the loopback
interface lead to all kinds of "interesting" problems :)
2014-12-09 18:45 G
On Wed, Dec 10, 2014 at 01:18:19AM +0800, Peizhen Guo wrote:
> I added some source files in ovs which implemented some new
> functions. When I’m trying to recompile the project, it always appears
> to have the fault: undefined reference to ‘xxx’, and the fault happens
> exactly where I invoke the n
On Mon, Dec 8, 2014 at 1:58 AM, Emil Flink wrote:
> Hi,
>
> I'm doing some testing with Open vSwitch 2.3.0 on Debian 7 (stable) compiled
> from source and have encountered a fairly weird error. I don't know if it is
> a problem with Debian or Open vSwitch.
>
> The mgmt0 interface comes up fully co
Hi all,
I added some source files in ovs which implemented some new functions. When I’m
trying to recompile the project, it always appears to have the fault: undefined
reference to ‘xxx’, and the fault happens exactly where I invoke the newly
written xxx function. To clarify, I’ve already incl
Hello,
I am wondering whether the OVS supports IP mulicast?
Thanks,
/DEAN
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
Hi,
It is a openstack setup that we are using. To be more clear with the
configuration:
-> we have set *mcast_snooping_enable=true* on *br-int* of OVS on
both the compute nodes.
-> *mcast-snooping-flood=true *for *Patch-tun* port of br-int on both
compute nodes ( so that the multi
Hi all,
Thanks again, because of your help it is working fine but i have a problem
with 2 compute nodes(each one is having different OVS),
below is the complete scenario.
[image: Inline image 1]
Here, when receiver VM1 sends IGMP v2 reports, it reaches to OVS2 also but
only OVS1 is able to Snoops
Just wanted to follow up on this with our solution. The OpenFlow library
soon to be backing Floodlight is OpenFlowJ-Loxigen. Using Loxigen (
https://github.com/floodlight/loxigen/wiki/OpenFlowJ-Loxi), we were able to
(1) define the additional Nicira extension OXMs as OpenFlow input, (2) add
the Mat
Hi Alex,
I'm using xen 4.3, directly as-is from debian-wheezy distribution.
Kernel 3.17.3.
Thanks,
Adam
W dniu 05.12.2014 o 17:51, Alex Wang pisze:
Hey Adam,
Sorry for the delayed reply, I have digressed by some issue,
Could I know the xen server version? I do not see any mem grow
on kvm,
Hi,
I'm doing some testing with Open vSwitch 2.3.0 on Debian 7 (stable)
compiled from source and have encountered a fairly weird error. I don't
know if it is a problem with Debian or Open vSwitch.
The mgmt0 interface comes up fully configured after reboot but is not
accessible until I have "used"
Hey Adam,
I'll try xen 4.3,
I tested on my xen6.2 build 70446 vm, did not see the memory util surge,
Thanks,
Alex Wang,
On Mon, Dec 8, 2014 at 8:17 AM, Adam Mazur wrote:
> Hi Alex,
>
> I'm using xen 4.3, directly as-is from debian-wheezy distribution.
> Kernel 3.17.3.
>
> Thanks,
> Adam
>
>
Hey Rahul,
The kernel version should not make a difference,
I'm curious, since ovs-2.3.0 is multithreaded, not sure how do you measure
the cpu usage to be 100%?
Also, could you post the full `mpstat -P ALL` output, so we can see the
distribution of cpu usage,
Thanks,
Alex Wang,
On Tue, Dec
Hi Alex,
Thanks for your help.
I am using the following command to test CPU usage.
mpstat -P ALL 1
I was using 3.12 kernel version and you are using 3.13.0-30-generic
version.Please let me know if this can be the issue??
On Sat, Dec 6, 2014 at 5:04 AM, Alex Wang wrote:
> Hey Rahul,
>
> Cou
19 matches
Mail list logo
