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
Ulli Horlacher frams...@rus.uni-stuttgart.de 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
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
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
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
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
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
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,
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
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
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.
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
12 matches
Mail list logo
