[lxc-users] lxc-start failed to retrieve the index for eth1

Hans Feldt hans.feldt at ericsson.com
Wed Nov 5 07:49:42 UTC 2014


udev problem?
http://www.turnkeylinux.org/docs/virtualization/udev-persistent-
net-generation

not sure if this applies to containers also

On 11/05/2014 06:28 AM, Christian Tardif wrote:
> Hi,
> I'm on CentOS 6.5, kernel 3.10.59, lxc-1.0.5 (have another installation
> with 1.0.6, and it gives the same result)
> Here's the sequence that leads to my problem:
> 1) Boot the host
>      - Have 4 different interfaces, only eth0 configured (my management
> ip), eth1, eth2, and eth3 are used as physical devices for containers
> 2) Boot a container (hooked to eth1)
>      - Works OK, got the IP in the container, all works great
> 3) Shutdown the container
> 4) Boot the container again and voilĂ !  Getting this:
>      - lax-start: failed to retrieve the index for eth1
> For now, the only way to get my container back is to.....  reboot the
> host  :-(
> Here's what I found on the list:
> https://www.mail-archive.com/lxc-users@lists.sourceforge.net/msg01769.html
> This is exactly my problem. My eth1 device became dev3. For sure I can
> use dev3 in the config file, and then the container will be able to
> reboot as I want...  until the host reboots. At boot time on the host,
> dev3 does not exists.
> The thread suggests that this problem has fixed in 0.7.4.1 but....  I'm
> on 1.0.5
> I found the issue. The problem comes, in fact, when, in the config file,
> you have different name between the link (the eth card on the host) and
> the nic name in the container. I always use to have eth0 as the first
> nic on a host, being physical, virtual, or container. And that's the
> problem, here. The config files says to use eth1, eth2, eth3, .....
> while all my containers are at eth0. If I change this behaviour so the
> physical link is eth1 and the container eth card is also eth1, then I
> get no problem at all. I can reboot the host, reboot the container
> hundreds of times, and it always work. But as soon as I get a
> discrepancy between the host eth card name and the container eth card
> name, I'm stucked.
> Has anyone experienced that this way?
>
> **
>
> *
> ------------------------------------------------------------------------
> *
> *
> Christian Tardif
> *christian.tardif at servinfo.ca <mailto:christian.tardif at servinfo.ca>
>
>
>
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>



More information about the lxc-users mailing list