That one is more worrisome. I believe that's an indication that packets are
getting dropped on the way to ovs-vswitchd. If you're using the software
kernel datapath, do you see the "lost" count going up in "ovs-dpctl show"? Are
you only seeing this when you first kick on the netperf tests? W
I was also getting the following warnings:
Jan 1 00:31:07 (none) daemon.warn ovs-vswitchd: 00017|dpif|WARN|system@br0:
recv failed (No buffer space available)
I looked up some old posts from OVS discuss (
http://www.mail-archive.com/discuss@openvswitch.org/msg03385.html), where
Ben had provided
Thanks for the explanation Justin.
I have lowered their log levels and I don't these warnings anymore. Thanks
for the help.
Regards.
-
Farrukh Aftab Khan
xFlow Research Inc.
On Wed, Dec 19, 2012 at 10:14 PM, Justin Pettit wrote:
> OVS logs these when the CPU usage spikes. That message stating
OVS logs these when the CPU usage spikes. That message stating the poll
interval was over 29 times the weighted mean interval triggered the coverage
counters below it. It shouldn't print that again unless there's another sudden
spike in CPU usage that would delay the time through the poll loop
Hi,
You could also try using virtual eth pairs, like this:
ip link add type veth
That will give you veth0 and veth1 which are tied together. Connect one of them
to your OVS bridge. Then give the other veth an IP address, and pump traffic
into that, OVS should receive it via its pair.
Best reg
Hello,
I am using OVS-1.7.1 on embedded Linux (kernel-2.6.32.27). I am generating
traffic at high data rate using 'netperf' and I get the following warnings:
1970-01-01T00:18:54Z|00029|timeval|WARN|51 ms poll interval (0 ms user, 50
ms system) is over 29 times the weighted mean interval 2 ms (242
