<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
<br>
Just to send a feedback... Looks like the problems were related to
the virtualbox network layer.<br>
<br>
I did the same setup on a Xen VM and till now, everything went
fine (except for the fact that the VMs are rebooting after 20
minutes, but I think this is duo to low setting on the gc_thresh1
(it's on 128) and I'm starting to troubleshoot it now! :P).<br>
<br>
Any way, thank very much for the insights! :)<br>
<br>
<br>
On 10/08/2012 04:02 PM, Leon Waldman wrote:<br>
</div>
<blockquote cite="mid:50732338.9080704@gmail.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hi all,<br>
<br>
<br>
I'm having a strange issue with the bridge on my lxc host.<br>
<br>
<br>
First, some background info:<br>
I'm running lxc version 0.75 on a CentOS 6.3 install with the
standard kernel (2.6.32-279.9.1.el6.i686).<br>
it's running inside a VirtualBox VM.<br>
<br>
I created 100 containers and named from 000 to 099. they are all
with sequential assigned IPs and macaddresses (from 10.0.1.0/8
till 10.0.1.99/8 | 80:04:C0:AB:00:00 till 80:04:C0:AB:00:63).<br>
<br>
<br>
When starting them in "mass" with something like:<br>
for i in `range 0 99`; do echo $i; lxc-start -n $i -d; done<br>
after a random number of containers is started the br0 bridge just
stops to answer for anything. It just freezes (it's easy to note
because I'm connecting to the host through ssh using the same
bridge).<br>
<br>
If I put a sleep 5 on the for above, things goes better, but then
one or two of the containers became a "remote bridge bomb". The
bridge stays working till a packet arrives to the "bomb"
container, and them again the entire bridge freezes. This
container bomb is also random.<br>
<br>
if I remove the problematic container iface from the bridge, it
unfreezes. If I add it again and send a packet... It freezes
again. If I stop the container and re-start it... all goes fine
and the issue vanish.<br>
<br>
<br>
From my point of view, looks like when the virtual iface is
created during the container start (if under load or with too much
concurrent starts... I don't know), sometimes something goes wrong
with the iface and it mess with the entire bridge if this "messy"
iface is attached.<br>
<br>
<br>
Do any one have any input on this (do this happened before? Is
there a limit for concurrent containers initializations? Is there
a kernel setting or some config that I could do to solve it)?<br>
<br>
<br>
In order to achieve what I need in production environment, I will
need to start and stop containers several times per minute. Do
this sound too problematic?<br>
<br>
<br>
If you guys need any additional information, please just let me
know. <br>
<br>
<br>
Thanks in advance<br>
<br>
--<br>
<span style="color: rgb(34, 34, 34); font-family: Times;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); font-size: 12px; "><a
moz-do-not-send="true" href="http://leonwaldman.com/"
target="_blank" style="color: green; "><b>Leon Waldman</b></a><br>
Senior Linux/UNIX SysAdmin & Consultant.<br>
Back-End & Infrastructure Architect.<br>
</span><span style="color: rgb(34, 34, 34); font-family: Times;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); display: inline
!important; float: none; font-size: medium; "></span><a
moz-do-not-send="true"
href="http://br.linkedin.com/in/leonwaldman" target="_blank"
style="color: rgb(17, 85, 204); font-family: Times; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); font-size: medium; "><img
src="cid:part2.03090009.01060509@gmail.com" alt="View Leon
Waldman's profile on LinkedIn" height="15" border="0"
width="80"></a><span style="color: rgb(34, 34, 34);
font-family: Times; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); display: inline !important; float: none; font-size:
medium; "> </span><br style="color: rgb(34, 34, 34);
font-family: Times; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); font-size: medium; ">
<a moz-do-not-send="true" href="https://twitter.com/lewaldman"
target="_blank" style="color: rgb(17, 85, 204); font-family:
Times; font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); font-size: medium; "><img
src="cid:part4.00080109.04020403@gmail.com"></a><br>
</blockquote>
<br>
</body>
</html>