[lxc-devel] lxc-stop: waiting for interface #X to come back

[Guido Trotter]

On Wed, Jun 24, 2009 at 12:22 PM, Daniel Lezcano<daniel.lezcano at free.fr> wrote:
> Daniel Lezcano wrote:
>> Markus Schuster wrote:
>>
>>> Hi list,
>>>
>>> I've a problem with lxc-stop I can't solve myself.
>>> I can use linux containers without problems so far, networking is working,
>>> but whenever I use lxc-stop, I get the following message:
>>>
>>> --- cut ---
>>> waiting for interface #X to come back
>>> .... [..] .... lxc 1245837641.613 ERROR lxc_conf - failed to remove the
>>> netdev
>>> --- cut ---
>>>
>>> The "[..]" stands for a huge amount of dots.
>>> I get this message for every interface I've associated with the container.
>>> I'm running Debian lenny with linux-image-2.6.29-2-686 and lxc (0.6.2) from
>>> unstable.
>>>
>>> Anybody an idea?
>>>
>>
>> You have to specify --with-kernel-release=2.6.29 for the configure script.
>>
>> The previous version of the network namespace didn't destroyed the
>> virtual interfaces so lxc was doing that for us. At present the kernel
>> automatically destroys the interfaces. If you have the wrong parameter
>> for the configure script, lxc may wait for these interfaces which were
>> already destroyed.
>>
>> As the definitive kernel behaviour is to destroy the virtual interface
>> belonging to the network namespace, this option will be removed for the
>> lxc version 0.6.3
>>
>
> oh sorry, I missed you were using a debian package. I guess Guido has to
> change the package debian script to specify this option.
>
> If you want you can use the tarball
> http://lxc.sourceforge.net/download/lxc/lxc-0.6.2.tar.gz
>
> configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
> --with-kernel-release=2.6.29
> if you are running on a 64bits host, you should specifiy
> --libdir=/usr/lib64 too.
>
> make && sudo make install && sudo lxc-setcap
>

I could, but does it make sense to do it immediately, if it's going to
be the default in 0.63?
And debian doesn't provide 2.6.29 yet, so you need to compile at least
the kernel yourself...

Guido