<HTML><HEAD>
<STYLE id=eMClientCss>
blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
.plain pre, .plain tt { font-family: monospace; font-size: 100%; font-weight: normal; font-style: normal; }
a img { border: 0px; }body {font-family: Tahoma;font-size: 12pt;}
.plain pre, .plain tt {font-family: Tahoma;font-size: 12pt;}</STYLE>
</HEAD>
<BODY>
<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>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)</DIV>
<DIV> </DIV>
<DIV>Here's the sequence that leads to my problem:</DIV>
<DIV> </DIV>
<DIV>1) Boot the host</DIV>
<DIV> - Have 4 different interfaces, only eth0 configured (my management ip), eth1, eth2, and eth3 are used as physical devices for containers</DIV>
<DIV> </DIV>
<DIV>2) Boot a container (hooked to eth1)</DIV>
<DIV> - Works OK, got the IP in the container, all works great</DIV>
<DIV> </DIV>
<DIV>3) Shutdown the container</DIV>
<DIV> </DIV>
<DIV>4) Boot the container again and voilà! Getting this:</DIV>
<DIV> - lax-start: failed to retrieve the index for eth1</DIV>
<DIV> </DIV>
<DIV>For now, the only way to get my container back is to..... reboot the host :-(</DIV>
<DIV> </DIV>
<DIV>Here's what I found on the list:</DIV>
<DIV> </DIV>
<DIV><A href="https://www.mail-archive.com/lxc-users@lists.sourceforge.net/msg01769.html">https://www.mail-archive.com/lxc-users@lists.sourceforge.net/msg01769.html</A></DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>The thread suggests that this problem has fixed in 0.7.4.1 but.... I'm on 1.0.5</DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>Has anyone experienced that this way?</DIV>
<DIV> </DIV>
<DIV id=signature_old>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: Tahoma">
<P><STRONG>
<DIV>
<HR>
</DIV><BR>Christian Tardif<BR></STRONG><A href="mailto:christian.tardif@servinfo.ca">christian.tardif@servinfo.ca</A>
<P></P></DIV></DIV>
<DIV> </DIV></BODY></HTML>