Is it true that only one lxc-wait can happen at a time??
I wrote some scripts that start and stop machines based on the run states of
other machines (this is for some fairly involved test scenarios).
Unfortunately, only the first script to run manages to lxc-wait -- the
rest bomb out with
I'm lazy too, that's why I let libvirt set up and maintain networking for me.
apt-get install libvirt
Now, set up your guests with:
lxc.network.type=veth
lxc.network.link=virbr0
lxc.network.flags=up
and NATing should just work. FWIW.
- Scott
On Fri, Sep 24, 2010 at 8:44 AM, Sebastien Pahl s...@dotcloud.com wrote:
I never tried libvirt (I guess all this XML scares me a bit:-P). Are
there any good examples of how to use it with lxc?
Agreed, but if you just use libvirt's network setup and not the rest
of it, no need to touch XML. It
When I call lxc-attach, I get an error:
# lxc-attach -n ubu-guest
lxc-attach: No such file or directory - failed to open '/proc/12580/ns/pid'
lxc-attach: failed to enter the namespace
Sure enough, /proc/12580/ns doesn't exist.
Is this because my kernel is too old? Or am I missing a mount or
I have lxc working pretty well on my Ubuntu Lucid box. Now I'm trying
to get it to work on my Fedora 13 laptop but I can't seem to get it to
connect to any guest consoles.
Here's an example:
[r...@lyra-f13 ubu-guest]# lxc-start -f config -n ubu-guest -o
$(tty) -l DEBUG
lxc-start
://lxc.sourceforge.net/patches/linux/
On Fri, Sep 17, 2010 at 08:54, Scott Bronson bron...@rinspin.com wrote:
When I call lxc-attach,...
--
Start uncovering the many advantages of virtual appliances
and start using
