Re: [Lxc-users] lxc-start "eats" eth1

2011-04-12 Thread Ulli Horlacher
On Tue 2011-04-12 (08:27), Serge Hallyn wrote:
> Quoting Ulli Horlacher (frams...@rus.uni-stuttgart.de):
> 
> > On Tue 2011-04-12 (09:19), Ulli Horlacher wrote:
> > > I use lxc with physical eth1.
> > > I can start the container, connect to it, etc. Everything looks ok. But
> > > when I stop the container and try to restart it, eth1 is no more availble.
> > > Looks lxc "eats" this interface. How can I free it (without rebooting the
> > > host (zoo))?
> > 
> > Addon:
> > 
> > This was with kernel 2.6.35-25-virtual
> 
> Could you try a newer kernel?

Same problem with 2.6.39-020639rc3-generic: eth1 will not come back after
container shutdown.


root@zoo:/lxc# uname -a
Linux zoo.rus.uni-stuttgart.de 2.6.39-020639rc3-generic #201104120912 SMP Tue 
Apr 12 09:16:19 UTC 2011 x86_64 GNU/Linux

root@zoo:/lxc# grep network ubuntu.cfg
lxc.network.type = phys
lxc.network.link = eth1
lxc.network.flags = up
lxc.network.name = eth0
lxc.network.mtu = 1500
lxc.network.ipv4 = 129.69.1.219/24

root@zoo:/lxc# l /proc/sys/net/ipv4/conf/
dRWX   - 2011-04-13 08:15 /proc/sys/net/ipv4/conf/all
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/br0
dRWX   - 2011-04-13 08:15 /proc/sys/net/ipv4/conf/default
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth0
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth1
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth2
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth3
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth4
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth5
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth6
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth7
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth8
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth9
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/lo
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/virbr0

root@zoo:/lxc# lxc-start -d -f /lxc/ubuntu.cfg -n ubuntu

root@zoo:/lxc# lxc-console -n ubuntu

Type  to exit the console
root@LXC:~# ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:50:56:8e:00:22
  inet addr:129.69.1.219  Bcast:129.69.1.255  Mask:255.255.255.0
  inet6 addr: fe80::250:56ff:fe8e:22/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:98 errors:0 dropped:0 overruns:0 frame:0
  TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:6675 (6.6 KB)  TX bytes:1386 (1.3 KB)

root@zoo:/lxc# lxc-stop -n ubuntu

root@zoo:/lxc# l /proc/sys/net/ipv4/conf/
dRWX   - 2011-04-13 08:15 /proc/sys/net/ipv4/conf/all
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/br0
dRWX   - 2011-04-13 08:15 /proc/sys/net/ipv4/conf/default
dRWX   - 2011-04-13 08:20 /proc/sys/net/ipv4/conf/dev3
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth0
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth2
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth3
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth4
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth5
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth6
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth7
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth8
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/eth9
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/lo
dRWX   - 2011-04-13 08:17 /proc/sys/net/ipv4/conf/virbr0

eth1 is now dev3

(How) can I rename it back?

Rebooting the host is not a solution :-}

-- 
Ullrich Horlacher  Server- und Arbeitsplatzsysteme
Rechenzentrum  E-Mail: horlac...@rus.uni-stuttgart.de
Universitaet Stuttgart Tel:++49-711-685-65868
Allmandring 30 Fax:++49-711-682357
70550 Stuttgart (Germany)  WWW:http://www.rus.uni-stuttgart.de/

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


[Lxc-users] How To Enable Networking In LXC Guests On Hetzner's DS Servers

2011-04-12 Thread yanu
I'm struggling with a same situation, discribed on this site:
 
http://www.howtoforge.com/how-to-enable-networking-in-xen-guests-on-hetzners-ds-servers-debian-etch
For now, i have 2 vserver-guests running and i want them to move to lxc.

How can i implement such a thing for lxc? I'm playing with debian squeeze.

I tried 2 scenario's by using a bridge br0, but that didn't work.

1. No configuration in /var/lib/lxc/vm0/config for the interface.
   Static configuration in /var/lib/lxc/vm0/rootfs/etc/network/interfaces

   In this case, i can access the net and install some packages.
   But the internet can't access the lxc-guest. Only ping works (level2).

2. Make a networkconfig in /var/lib/lxc/vm0/config (veth) as discribed in
   http://blog.foaa.de/2010/05/lxc-on-debian-squeeze/
   No access from both ways.

I tested this at home within the same subnet, all worked well.
If i set the lxc-guest to a different subnet, i see the same problems as 
discribed above.

Thx if you can help me.

-- 
Groeten Lieven Baes aka yanu
http://www.debian.org http://www.ubuntu-be.org
http://www.libreoffice.orghttp://nl.openoffice.org

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] Can't execute lxc-execute /bin/bash

2011-04-12 Thread Justin Cormack
On Tue, 2011-04-12 at 12:11 +0100, Justin Cormack wrote:
> On Mon, 2011-04-11 at 18:07 -0500, Serge Hallyn wrote:
> > Quoting Krzysztof Karwacki (krzys...@motokirc.pl):
> > > Hi!
> > > 
> > > I Compiled procfs from lxc sources, but when i want to   lxc-execute –n 
> > > vm0 /bin/bash I’ve got error.
> > > 
> > > root@debian:~# lxc-execute -n vm0 /bin/bash
> > > lxc-execute: No such file or directory - failed to exec 
> > > /usr/lib/lxc/lxc-init
> > 
> > Does /usr/lib/lxc/lxc-init exist on the host?
> > 
> > When I've played with custom templates based of the ssh template, I've
> > had similar troubles, and I think I usually ended up trying putting
> > lxc-init onto the guest.
> 
> You dont need lxc-init on the guest. It is executed before setting the
> filesystem namespace. Looks like /usr/lib/lxc/lxc-init  is not
> installed/installed in the wrong place (or wrong permissions?).

Sorry thats completely untrue. I forgot I was bind mounting /lib
and /usr/lib so it was just there, and just ran into the same error when
I didnt. You *do* need /usr/lib/lxc/lxc-init (and the libraries it
needs) inside your guest.

Justin



--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] lxc-start "eats" eth1

2011-04-12 Thread Daniel Lezcano
On 04/12/2011 03:44 PM, Ulli Horlacher wrote:
> On Tue 2011-04-12 (15:37), Daniel Lezcano wrote:
>
>>> Shouldn't I see it under another name then?
>>>
>>> I see only:
>>>
>>> root@zoo:~# ll /proc/sys/net/ipv4/conf/
>>> dr-xr-xr-x root root   - 2011-04-12 13:33:12 
>>> /proc/sys/net/ipv4/conf/all
>>> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
>>> /proc/sys/net/ipv4/conf/br0
>>> dr-xr-xr-x root root   - 2011-04-12 13:33:12 
>>> /proc/sys/net/ipv4/conf/default
>>> dr-xr-xr-x root root   - 2011-04-12 15:31:17 
>>> /proc/sys/net/ipv4/conf/dev3
>>
>> I think it is dev3. You can check with the index.
>
> You are right!
>
> root@zoo:~# ethtool dev3
> Settings for dev3:
>  Supported ports: [ TP ]
>  Supported link modes:   10baseT/Half 10baseT/Full
>  100baseT/Half 100baseT/Full
>  1000baseT/Full
>  Supports auto-negotiation: Yes
>  Advertised link modes:  10baseT/Half 10baseT/Full
>  100baseT/Half 100baseT/Full
>  1000baseT/Full
>  Advertised pause frame use: No
>  Advertised auto-negotiation: Yes
>  Link partner advertised link modes:  Not reported
>  Link partner advertised pause frame use: No
>  Link partner advertised auto-negotiation: No
>  Speed: 1000Mb/s
>  Duplex: Full
>  Port: Twisted Pair
>  PHYAD: 0
>  Transceiver: internal
>  Auto-negotiation: on
>  MDI-X: Unknown
>  Supports Wake-on: d
>  Wake-on: d
>  Current message level: 0x0007 (7)
>  Link detected: yes
>
>
> Is there a hack to rename it?
> Or to tell lxc to use this interface name instead?
>
> root@zoo:~# mv /proc/sys/net/ipv4/conf/dev3 /proc/sys/net/ipv4/conf/eth1
> mv: cannot move `/proc/sys/net/ipv4/conf/dev3' to 
> `/proc/sys/net/ipv4/conf/eth1': No such file or directory


Can't you upgrade to lxc-0.7.4.1 ?

http://lxc.sourceforge.net/download/lxc/lxc-0.7.4.1.tar.gz






















































Sauf indication contraire ci-dessus:
Compagnie IBM France
Siège Social : Tour Descartes, 2, avenue Gambetta, La Défense 5, 92400
Courbevoie
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 542.737.118 ?
SIREN/SIRET : 552 118 465 02430

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] lxc-start "eats" eth1

2011-04-12 Thread Ulli Horlacher
On Tue 2011-04-12 (15:37), Daniel Lezcano wrote:

> > Shouldn't I see it under another name then?
> >
> > I see only:
> >
> > root@zoo:~# ll /proc/sys/net/ipv4/conf/
> > dr-xr-xr-x root root   - 2011-04-12 13:33:12 
> > /proc/sys/net/ipv4/conf/all
> > dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> > /proc/sys/net/ipv4/conf/br0
> > dr-xr-xr-x root root   - 2011-04-12 13:33:12 
> > /proc/sys/net/ipv4/conf/default
> > dr-xr-xr-x root root   - 2011-04-12 15:31:17 
> > /proc/sys/net/ipv4/conf/dev3
> 
> I think it is dev3. You can check with the index.

You are right!

root@zoo:~# ethtool dev3
Settings for dev3:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes:  Not reported
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: No
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: d
Wake-on: d
Current message level: 0x0007 (7)
Link detected: yes


Is there a hack to rename it? 
Or to tell lxc to use this interface name instead?

root@zoo:~# mv /proc/sys/net/ipv4/conf/dev3 /proc/sys/net/ipv4/conf/eth1
mv: cannot move `/proc/sys/net/ipv4/conf/dev3' to 
`/proc/sys/net/ipv4/conf/eth1': No such file or directory




-- 
Ullrich Horlacher  Server- und Arbeitsplatzsysteme
Rechenzentrum  E-Mail: horlac...@rus.uni-stuttgart.de
Universitaet Stuttgart Tel:++49-711-685-65868
Allmandring 30 Fax:++49-711-682357
70550 Stuttgart (Germany)  WWW:http://www.rus.uni-stuttgart.de/

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] lxc-start "eats" eth1

2011-04-12 Thread Daniel Lezcano
On 04/12/2011 03:35 PM, Ulli Horlacher wrote:
> On Tue 2011-04-12 (15:24), Daniel Lezcano wrote:
>> On 04/12/2011 09:19 AM, Ulli Horlacher wrote:
>>
>>> I use lxc with physical eth1.
>>> I can start the container, connect to it, etc. Everything looks ok. But
>>> when I stop the container and try to restart it, eth1 is no more availble.
>>> Looks lxc "eats" this interface. How can I free it (without rebooting the
>>> host (zoo))?
>>
>> It is probable it was renamed by the kernel when the container exited.
>
> Shouldn't I see it under another name then?
>
> I see only:
>
> root@zoo:~# ll /proc/sys/net/ipv4/conf/
> dr-xr-xr-x root root   - 2011-04-12 13:33:12 
> /proc/sys/net/ipv4/conf/all
> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/br0
> dr-xr-xr-x root root   - 2011-04-12 13:33:12 
> /proc/sys/net/ipv4/conf/default
> dr-xr-xr-x root root   - 2011-04-12 15:31:17 
> /proc/sys/net/ipv4/conf/dev3

I think it is dev3. You can check with the index.

> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/eth0
> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/eth2
> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/eth3
> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/eth4
> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/eth5
> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/eth6
> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/eth7
> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/eth8
> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/eth9
> dr-xr-xr-x root root   - 2011-04-12 15:30:22 
> /proc/sys/net/ipv4/conf/lo
>
>
>> I think it was fixed by:
>>
>> http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=d472214b8342a0b705ed40e358cf9caff427042a
>>
>> This fix is available in the 0.7.4.1 version
>
> I use lxc provided by Ubuntu 10.04
>
> Must I patch the kernel?
>
>


--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] lxc-start "eats" eth1

2011-04-12 Thread Ulli Horlacher
On Tue 2011-04-12 (15:24), Daniel Lezcano wrote:
> On 04/12/2011 09:19 AM, Ulli Horlacher wrote:
> 
> > I use lxc with physical eth1.
> > I can start the container, connect to it, etc. Everything looks ok. But
> > when I stop the container and try to restart it, eth1 is no more availble.
> > Looks lxc "eats" this interface. How can I free it (without rebooting the
> > host (zoo))?
> 
> It is probable it was renamed by the kernel when the container exited.

Shouldn't I see it under another name then?

I see only:

root@zoo:~# ll /proc/sys/net/ipv4/conf/
dr-xr-xr-x root root   - 2011-04-12 13:33:12 
/proc/sys/net/ipv4/conf/all
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/br0
dr-xr-xr-x root root   - 2011-04-12 13:33:12 
/proc/sys/net/ipv4/conf/default
dr-xr-xr-x root root   - 2011-04-12 15:31:17 
/proc/sys/net/ipv4/conf/dev3
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/eth0
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/eth2
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/eth3
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/eth4
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/eth5
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/eth6
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/eth7
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/eth8
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/eth9
dr-xr-xr-x root root   - 2011-04-12 15:30:22 
/proc/sys/net/ipv4/conf/lo


> I think it was fixed by:
> 
> http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=d472214b8342a0b705ed40e358cf9caff427042a
> 
> This fix is available in the 0.7.4.1 version

I use lxc provided by Ubuntu 10.04

Must I patch the kernel?


-- 
Ullrich Horlacher  Server- und Arbeitsplatzsysteme
Rechenzentrum  E-Mail: horlac...@rus.uni-stuttgart.de
Universitaet Stuttgart Tel:++49-711-685-65868
Allmandring 30 Fax:++49-711-682357
70550 Stuttgart (Germany)  WWW:http://www.rus.uni-stuttgart.de/

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] lxc-start "eats" eth1

2011-04-12 Thread Daniel Lezcano
On 04/12/2011 01:36 PM, Ulli Horlacher wrote:
> On Tue 2011-04-12 (09:19), Ulli Horlacher wrote:
>> I use lxc with physical eth1.
>> I can start the container, connect to it, etc. Everything looks ok. But
>> when I stop the container and try to restart it, eth1 is no more availble.
>> Looks lxc "eats" this interface. How can I free it (without rebooting the
>> host (zoo))?
>
> Addon:
>
> This was with kernel 2.6.35-25-virtual
>
> With kernel 2.6.32-30-server I even cannot start the container:

Yes, in order to be able to use a physical netdev to a container, the 
/sys/class/net per namespace is needed which is available in mainstream 
since the 2.6.35 kernel version.

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] lxc-start "eats" eth1

2011-04-12 Thread Serge Hallyn
Quoting Ulli Horlacher (frams...@rus.uni-stuttgart.de):
> On Tue 2011-04-12 (09:19), Ulli Horlacher wrote:
> > I use lxc with physical eth1.
> > I can start the container, connect to it, etc. Everything looks ok. But
> > when I stop the container and try to restart it, eth1 is no more availble.
> > Looks lxc "eats" this interface. How can I free it (without rebooting the
> > host (zoo))?
> 
> Addon:
> 
> This was with kernel 2.6.35-25-virtual

Could you try a newer kernel?

2.6.32 is expected to fail entirely because it did not support physical
NICs in containers.  I seem to recall some churn about how to handle
devices when a netns is destroyed.  At one point they were moved back
to the initial netns.

If the behavior you're seeing with 2.6.35-25-virtual is still happening
with 2.6.39, then lxc will need to work around that by moving the nic
back to the host netns before shutting down the container (or kernel
behavior fixed/changed).

thanks,
-serge

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] lxc-start "eats" eth1

2011-04-12 Thread Daniel Lezcano
On 04/12/2011 09:19 AM, Ulli Horlacher wrote:
> I use lxc with physical eth1.
> I can start the container, connect to it, etc. Everything looks ok. But
> when I stop the container and try to restart it, eth1 is no more availble.
> Looks lxc "eats" this interface. How can I free it (without rebooting the
> host (zoo))?

It is probable it was renamed by the kernel when the container exited.

I think it was fixed by:

http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=d472214b8342a0b705ed40e358cf9caff427042a

This fix is available in the 0.7.4.1 version

Thanks
   -- Daniel

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] lxc-start "eats" eth1

2011-04-12 Thread Ulli Horlacher
On Tue 2011-04-12 (09:19), Ulli Horlacher wrote:
> I use lxc with physical eth1.
> I can start the container, connect to it, etc. Everything looks ok. But
> when I stop the container and try to restart it, eth1 is no more availble.
> Looks lxc "eats" this interface. How can I free it (without rebooting the
> host (zoo))?

Addon:

This was with kernel 2.6.35-25-virtual

With kernel 2.6.32-30-server I even cannot start the container:

root@zoo:~# lxc-start -f /lxc/ubuntu.cfg -n ubuntu
lxc-start: failed to move 'eth1' to the container
lxc-start: failed to create the configured network
lxc-start: failed to spawn '/sbin/init'

though eth1 is there:

root@zoo:~# ethtool eth1
Settings for eth1:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes:  Not reported
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: No
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: d
Wake-on: d
Current message level: 0x0007 (7)
Link detected: no

-- 
Ullrich Horlacher  Server- und Arbeitsplatzsysteme
Rechenzentrum  E-Mail: horlac...@rus.uni-stuttgart.de
Universitaet Stuttgart Tel:++49-711-685-65868
Allmandring 30 Fax:++49-711-682357
70550 Stuttgart (Germany)  WWW:http://www.rus.uni-stuttgart.de/

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] Can't execute lxc-execute /bin/bash

2011-04-12 Thread Justin Cormack
On Mon, 2011-04-11 at 18:07 -0500, Serge Hallyn wrote:
> Quoting Krzysztof Karwacki (krzys...@motokirc.pl):
> > Hi!
> > 
> > I Compiled procfs from lxc sources, but when i want to   lxc-execute –n vm0 
> > /bin/bash I’ve got error.
> > 
> > root@debian:~# lxc-execute -n vm0 /bin/bash
> > lxc-execute: No such file or directory - failed to exec 
> > /usr/lib/lxc/lxc-init
> 
> Does /usr/lib/lxc/lxc-init exist on the host?
> 
> When I've played with custom templates based of the ssh template, I've
> had similar troubles, and I think I usually ended up trying putting
> lxc-init onto the guest.

You dont need lxc-init on the guest. It is executed before setting the
filesystem namespace. Looks like /usr/lib/lxc/lxc-init  is not
installed/installed in the wrong place (or wrong permissions?).

Justin



--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] native (non-NAT) routing?

2011-04-12 Thread Ulli Horlacher
On Tue 2011-04-12 (09:28), Toens Bueker wrote:

> > zoo runs on virtual hardware (VMware ESXi), where vms2 runs on real
> > hardware. I assume now, lxc bridge networking is not compatible with ESXi!
> 
> What is configured on ESXi?

A virtual switch for this VLAN. I have tested it with and without
promiscous mode.


-- 
Ullrich Horlacher  Server- und Arbeitsplatzsysteme
Rechenzentrum  E-Mail: horlac...@rus.uni-stuttgart.de
Universitaet Stuttgart Tel:++49-711-685-65868
Allmandring 30 Fax:++49-711-682357
70550 Stuttgart (Germany)  WWW:http://www.rus.uni-stuttgart.de/

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] native (non-NAT) routing?

2011-04-12 Thread Toens Bueker
Ulli Horlacher  wrote:

> > host  zoo 129.69.1.39
> > container LXC 129.69.1.219
> > router129.69.1.254
> > 
> > In LXC.conf is:
> > 
> > lxc.utsname = LXC
> > lxc.network.type = veth
> > lxc.network.link = br0
> > lxc.network.flags = up
> > lxc.network.name = eth0
> > lxc.network.mtu = 1500
> > lxc.network.ipv4 = 129.69.1.219/24
> 
> Same configuration on another host ("vms2", with another ip) works as
> expected!
> 
> zoo runs on virtual hardware (VMware ESXi), where vms2 runs on real
> hardware. I assume now, lxc bridge networking is not compatible with ESXi!

What is configured on ESXi?

Regards,
Töns
-- 
There is no safe distance.

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


[Lxc-users] lxc-start "eats" eth1

2011-04-12 Thread Ulli Horlacher

I use lxc with physical eth1.
I can start the container, connect to it, etc. Everything looks ok. But
when I stop the container and try to restart it, eth1 is no more availble.
Looks lxc "eats" this interface. How can I free it (without rebooting the
host (zoo))?


root@zoo:/lxc# cat ubuntu.cfg
lxc.utsname = LXC
lxc.tty = 4
lxc.pts = 1024
#lxc.network.type = veth
#lxc.network.link = br0
lxc.network.type = phys
lxc.network.link = eth1
lxc.network.flags = up
#lxc.network.hwaddr = 00:50:56:00:00:01
lxc.network.name = eth0
lxc.network.mtu = 1500
lxc.network.ipv4 = 129.69.1.219/24
lxc.rootfs = /lxc/ubuntu
lxc.mount = /lxc/ubuntu.fstab
# which CPUs
lxc.cgroup.cpuset.cpus = 0
lxc.cgroup.devices.deny = a
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
lxc.cgroup.devices.allow = c 4:0 rwm
lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
# restrict capabilities, see: man capabilities
lxc.cap.drop = sys_module
lxc.cap.drop = mac_override
lxc.cap.drop = sys_admin


root@zoo:/lxc# ethtool eth1
Settings for eth1:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes:  Not reported
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: No
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: d
Wake-on: d
Current message level: 0x0007 (7)
Link detected: yes


root@zoo:/lxc# lxc-start -f /lxc/ubuntu.cfg -n ubuntu &
[1] 1679
init: rc-sysinit main process (30) killed by TERM signal
 * Starting NTP server ntpd
   ...done.

root@zoo:/lxc# lxc-console -n ubuntu

Type  to exit the console

root@ubuntu:~# ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:50:56:8e:00:22
  inet addr:129.69.1.219  Bcast:0.0.0.0  Mask:255.255.255.0
  inet6 addr: fe80::250:56ff:fe8e:22/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:115 errors:0 dropped:0 overruns:0 frame:0
  TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:7695 (7.6 KB)  TX bytes:1344 (1.3 KB)

root@ubuntu:~#

root@zoo:/lxc# lxc-stop -n ubuntu
[1]+  Exit 137lxc-start -f /lxc/ubuntu.cfg -n ubuntu

root@zoo:/lxc# lxc-start -f /lxc/ubuntu.cfg -n ubuntu
lxc-start: failed to retrieve the index for eth1
lxc-start: failed to create netdev
lxc-start: failed to create the network
lxc-start: failed to spawn '/sbin/init'
lxc-start: No such file or directory - failed to remove cgroup '/cgroup/ubuntu'

root@zoo:/lxc# ethtool eth1
Settings for eth1:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available

-- 
Ullrich Horlacher  Server- und Arbeitsplatzsysteme
Rechenzentrum  E-Mail: horlac...@rus.uni-stuttgart.de
Universitaet Stuttgart Tel:++49-711-685-65868
Allmandring 30 Fax:++49-711-682357
70550 Stuttgart (Germany)  WWW:http://www.rus.uni-stuttgart.de/

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users