[lxc-users] lx-start taking a long time if veth is not added to lxcbr0Š

[Anjali Kulkarni]

Thanks, yes, it is supposed to have dhcp via libvirt, and another VM's IP
in there:

br-int's current xml config has:

<ip address="172.16.0.3" netmask="255.255.0.0">
    <dhcp>
      <host ip="172.16.0.1" mac="0A:00:DE:C0:DE:01" name="vRE" />
    </dhcp>

 I added the foll. Line to br-int, but does not help:

<host ip="172.16.0.2" mac="00:16:3e:d9:c0:ce" name="vpfe" />



?

Anjali

On 10/1/14 2:19 PM, "Stéphane Graber" <stgraber at ubuntu.com> wrote:

>On Wed, Oct 01, 2014 at 08:53:07PM +0000, Anjali Kulkarni wrote:
>> Hi,
>> 
>> I notice that If I add my beth link to any other bridge except lxcbr0,
>>my ubuntu container takes a really long time to boot up, and seems to
>>hang/wait for a long time after this statement:
>>  * Starting Bridge socket events into upstart   ...done.
>> 
>> My config file is:
>> 
>> ŠŠ.
>> # Network configuration
>> lxc.network.type = veth
>> lxc.network.link = br-int
>> lxc.network.ipv4 = 172.16.0.2
>> lxc.network.name = eth0
>> lxc.network.flags = up
>> lxc.network.hwaddr = 00:16:3e:d9:c0:ce
>> 
>> I found out, that if I keep
>> lxc.network.link = lxcbr0
>> Instead of
>> lxc.network.link = br-int
>> 
>> It boots up really fast.
>> Is there any way to get around this? I don't want to add the veth
>>interface to lxcbr0, but to br-int..
>> 
>> Anjali
>
>
>Do you have a dhcp server running on br-int?
>
>If the container takes 2 minutes to boot, that's because it didn't get
>an IP address and eventually gave up.
>
>-- 
>Stéphane Graber
>Ubuntu developer
>http://www.ubuntu.com