Dear Michael,
I always hate replying to my own posts but I have stumbled onto some
interesting clarification as I've continued to play with this...
Below in-line.
[...]
Again a well-done investigation. For everyone who don't have the time to
carefully read this threads, i want to sum the
I always hate replying to my own posts but I have stumbled onto some
interesting clarification as I've continued to play with this...
Below in-line.
On Tue, 2011-12-13 at 01:30 -0500, Michael H. Warfield wrote:
On Mon, 2011-12-12 at 08:43 +0100, Ulli Horlacher wrote:
On Sun 2011-12-11
On 12/12/2011 04:48 AM, Derek Simkowiak wrote:
When there are only one bridge on the system or the bridges are not
connected together, this option is pointless and we can set the delay to
'0'. That makes the port to be enabled instantaneously, hence the
container can access the network
On Mon, 2011-12-12 at 08:43 +0100, Ulli Horlacher wrote:
On Sun 2011-12-11 (19:48), Derek Simkowiak wrote:
The problem is not related to the setfd option. It is caused by
the bridge acquired a new MAC address. Libvirt already has a fix for
this, and there is a patch in the works
On 12/08/2011 09:25 AM, Ulli Horlacher wrote:
On Thu 2011-12-08 (07:39), Daniel Lezcano wrote:
On 12/08/2011 12:38 AM, Joseph Heck wrote:
I've been seeing a pause in the whole networking stack when starting
and stopping LXC - it seems to be somewhat intermittent, but happens
reasonably
When there are only one bridge on the system or the bridges are not
connected together, this option is pointless and we can set the delay to
'0'. That makes the port to be enabled instantaneously, hence the
container can access the network immediately after the start.
As previously posted,
On 08/12/11 19:39, Daniel Lezcano wrote:
On 12/08/2011 12:38 AM, Joseph Heck wrote:
I've been seeing a pause in the whole networking stack when starting
and stopping LXC - it seems to be somewhat intermittent, but happens
reasonably consistently the first time I start up the LXC.
I'm using
On Thu, 2011-12-08 at 19:47 +1300, Gary Ballantyne wrote:
On 08/12/11 19:39, Daniel Lezcano wrote:
On 12/08/2011 12:38 AM, Joseph Heck wrote:
I've been seeing a pause in the whole networking stack when starting
and stopping LXC - it seems to be somewhat intermittent, but happens
/I've been seeing a pause in the whole networking stack/...
It's because you use bridged networking. A Linux host bridge will
sometimes inherit a new MAC address, causing a ~4 second network
blackout while ARP tables refresh. This is inconvenient for
server-based virtualization
On 12/08/2011 12:38 AM, Joseph Heck wrote:
I've been seeing a pause in the whole networking stack when starting
and stopping LXC - it seems to be somewhat intermittent, but happens
reasonably consistently the first time I start up the LXC.
I'm using ubuntu 11.10, which is using LXC 0.7.5
10 matches
Mail list logo
