[Lxc-users] lxc-start "eats" eth1

Serge Hallyn serge.hallyn at canonical.com
Tue Apr 12 13:27:42 UTC 2011


Quoting Ulli Horlacher (framstag at rus.uni-stuttgart.de):
> On Tue 2011-04-12 (09:19), Ulli Horlacher wrote:
> > I use lxc with physical eth1.
> > I can start the container, connect to it, etc. Everything looks ok. But
> > when I stop the container and try to restart it, eth1 is no more availble.
> > Looks lxc "eats" this interface. How can I free it (without rebooting the
> > host (zoo))?
> 
> Addon:
> 
> This was with kernel 2.6.35-25-virtual

Could you try a newer kernel?

2.6.32 is expected to fail entirely because it did not support physical
NICs in containers.  I seem to recall some churn about how to handle
devices when a netns is destroyed.  At one point they were moved back
to the initial netns.

If the behavior you're seeing with 2.6.35-25-virtual is still happening
with 2.6.39, then lxc will need to work around that by moving the nic
back to the host netns before shutting down the container (or kernel
behavior fixed/changed).

thanks,
-serge




More information about the lxc-users mailing list