[Lxc-users] LXC no connectivity after first "boot" of the guest

[Klemens Rauch]

On 10.08.2012 13:33, Fajar A. Nugraha wrote:
> On Fri, Aug 10, 2012 at 3:23 PM, Klemens Rauch
> <klemens.rauch at rolmail.net> wrote:
>> Hi,
>>
>> I'm a beginner with lxc and and have been making my way thru the
>> documentation and several mailing lists.
>>
>> Now I have problem which I can't resolve by myself.
>> First of all some general Information about my Infrastructure:
>> I'm running a Debian Squeeze Server with a (3.2.0-0.bpo.2-amd64) Kernel,
>> running lxc (0.8.0~rc1-8) from testing repositories.
>> cgroups mounted, bridge-utils installed and configured, debootstrap and
>> libvirt-bin too.
>>
>> I made 4 wheezy guests via:
>> lxc-create -n xxx -t debian
>
> IIRC debian only support using lxc-debconf, not lxc-debian, so I
> wouldn't be surprised if you found a problem which won't be fixed.
>
>> Same behaviour with the other 3 guests. First boot everything works like
>> a charm than after the first time no connectivity to the rest of the world.
>
> What does "brctl show" on the host looks like:
> - before you start any guest
> - when the first guest is started
> - after the first guest is down
> - when the second guest is started (or is it the same guest restarted?)
>
> Just in case there were some problems with bridging on the host side.
>

 > IIRC debian only support using lxc-debconf, not lxc-debian, so I
 > wouldn't be surprised if you found a problem which won't be fixed.
I tried to create one with
lxc-create -n xxx -t debconf
But it crashes with the following output:
Downloading minimal system...
cd: 381: can't cd to http://ftp.debian.org
Failed to download the rootfs, aborting.
Failed to download base system
failed to install system
failed to execute template 'debconf'
aborted

Is there somewhere a documentation to use lxc with debconf as template?

 > What does "brctl show" on the host looks like:
 > - before you start any guest
bridge name	bridge id		STP enabled	interfaces
br0		8000.5404a6b49e33	no		eth0
 > - when the first guest is started
bridge name	bridge id		STP enabled	interfaces
br0		8000.5404a6b49e33	no		eth0
							vethCRhIeB
 > - after the first guest is down
bridge name	bridge id		STP enabled	interfaces
br0		8000.5404a6b49e33	no		eth0
 > - when the second guest is started (or is it the same guest restarted?)
all guests are started
bridge name	bridge id		STP enabled	interfaces
br0		8000.5404a6b49e33	no		eth0
							vethE70uMb
							vethQp9dQg
							vethpNks24
							veths5j2kt

and with a freshly installed guest
bridge name	bridge id		STP enabled	interfaces
br0		8000.5404a6b49e33	no		eth0
							vethmALo2v
after the restart of the fresly installed guest
bridge name	bridge id		STP enabled	interfaces
br0		8000.5404a6b49e33	no		eth0
							vethLXYG0R

dmesg output:
[20497.182908] ADDRCONF(NETDEV_UP): vethLXYG0R: link is not ready
[20497.280198] ADDRCONF(NETDEV_CHANGE): vethLXYG0R: link becomes ready
[20497.281207] br0: port 2(vethLXYG0R) entering forwarding state
[20497.282181] br0: port 2(vethLXYG0R) entering forwarding state
[20507.597801] vethLXYG0R: no IPv6 routers present
[20507.725734] eth0: no IPv6 routers present
[20511.004005] martian source 176.9.xxx.xxx from 195.254.xx.xx, on dev eth0
[20511.004976] ll header: 00:50:56:00:1a:b7:78:fe:3d:46:ed:88:08:00
[20514.008501] martian source 176.9.xxx.xxx from 195.254.xxx.xxx, on dev 
eth0
[20514.009490] ll header: 00:50:56:00:1a:b7:78:fe:3d:46:ed:88:08:00


Greets
Klemens