Brian K. White wrote:
Michael H. Warfield wrote:
On Fri, 2010-02-12 at 11:37 -0500, Brian K. White wrote:
So my question is, is 02:x:x:x:x:x in some way non-routable just
because it sets the locally-administered bit?
I use that all the time without any problems. It may be something
Brian K. White wrote:
However, now when I go to make a 2nd container, I can't start it.
I can create it, but not execute or start.
[...]
Well I'm more boggled now.
I stopped my first container nj12.
lxc-ls shows nothing, screen -ls shows nothing, mount shows nothing extra,
yet trying to start
On 5/10/2010 10:48 AM, Daniel Lezcano wrote:
Ferenc Wagner wrote:
Daniel Lezcanodaniel.lezc...@free.fr writes:
Ferenc Wagner wrote:
Ferenc Wagnerwf...@niif.hu writes:
Daniel Lezcanodlezc...@fr.ibm.com writes:
Ferenc Wagner wrote:
On 5/26/2010 4:54 AM, Ralf Schmitt wrote:
Daniel Lezcanodlezc...@fr.ibm.com writes:
This is internal stuff of lxc. Before this commit, several temporary
directories were created and never destroyed, polluting '/tmp'.
In order to do pivot_root, we have to mount --bind the rootfs
On 6/7/2010 7:51 PM, Nirmal Guhan wrote:
Hi,
Is there a way to use shared memory between the containers? Any other
better/faster IPC mechanisms? I don't want to use sockets.
Please let me know.
Fifos on shared filesystem on the host?
Multiply hardlinked files on the host which appear in
On 8/17/2010 11:43 AM, Gordon Henderson wrote:
On Fri, 13 Aug 2010, Clemens Perz wrote:
Hi!
I used to run lxc-stop on my system containers when I actually want to
run a halt. Only today I noticed, that stop actually kills all
processes, not really doing a halt. I went through the lxc
On 8/27/2010 8:20 AM, Matto Fransen wrote:
Hi,
On Fri, Aug 27, 2010 at 11:27:16AM +0200, Sebastien Douche wrote:
I created a container with an interface. I stop it, I change the MAC
address, restart it:
lxc-start: ioctl failure : Cannot assign requested address
lxc-start: failed to setup
On 9/16/2010 3:36 AM, Jue Hong wrote:
As I understand, running one application with the command lxc-execute
will create a container instance. E.g., by running lxc-execute -n foo
/bin/bash, a container named foo will be created, and I can find a foo
directory under the mounted cgroup directory,
I have lxc 0.7.2 on openSUSE 11.2, which is kernel 2.6.31
I get this all the time on my other boxes which up to now have been lxc
0.6.5 on the same kernel, but I've lived with it by just trying to never
reboot containers, and only using containers for services that can stand
to be rebooted so
On 11/5/2010 1:34 PM, Serge E. Hallyn wrote:
A few comments:
1. To remove the directories, rmdir all descendent directories. I'd
think something like 'find . -type d -print0 | xargs rmdir' would
do.
I can't delete _anything_ in there. Not a file, let alone a directory
with or
On 11/5/2010 1:34 PM, Serge E. Hallyn wrote:
A few comments:
1. To remove the directories, rmdir all descendent directories. I'd
think something like 'find . -type d -print0 | xargs rmdir' would
do.
2. You can prevent this from happening by using a notify-on-release
handler.
On 11/5/2010 4:20 PM, Serge E. Hallyn wrote:
Quoting Brian K. White (br...@aljex.com):
I don't know how to track down if there is possibly some process that is
part of the cgroup even though lxc-ps doesn't show any.
Examine every single process and verify that it's part of the host or
another
On 11/8/2010 1:14 PM, Michael H. Warfield wrote:
On Mon, 2010-11-01 at 08:40 -0500, Serge E. Hallyn wrote:
Quoting Walter Stanish (walter.stan...@saffrondigital.com):
http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commitdiff_plain;h=c01d62f21b21ba6c2b8b78ab3c2b37cc8f8fd265
This
On 11/8/2010 1:32 PM, Serge Hallyn wrote:
Quoting Brian K. White (br...@aljex.com):
But also, since upgrading to kernel 2.6.36 (and already using lxc 0.7.2)
I haven't had to delete any cgroups manually anyways. It's probably not
my release_agent because I just noticed I didn't have a working
containers.
# For lxc 0.7.2 which doesn't require an external monitor process to perform
# the lxc-stop when a containers init process requests init 0|1|6 .
#
# 20101108 - Brian K. White - br...@aljex.com
#
### BEGIN INIT INFO
# Provides: lxc
# Required-Start:$ALL
# Should-Start
On 12/6/2010 3:01 AM, Trent W. Buck wrote:
Trent W. Buck writes:
This post describes my attempts to get clean shutdown of Ubuntu 10.04
containers. The goal here is that a shutdown -h now of the dom0
should not result in a potentially inconsistent domU postgres database,
cf. a naive
On 12/6/2010 3:34 PM, Michael H. Warfield wrote:
On Mon, 2010-12-06 at 12:38 -0500, Brian K. White wrote:
On 12/6/2010 2:42 AM, Trent W. Buck wrote:
This post describes my attempts to get clean shutdown of Ubuntu 10.04
containers. The goal here is that a shutdown -h now of the dom0
should
On 12/13/2010 1:03 PM, Stéphane Graber wrote:
On Tue, 2010-11-30 at 03:06 +, Serge E. Hallyn wrote:
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
On 11/29/2010 03:53 PM, Serge E. Hallyn wrote:
Hi,
at UDS-N we had a session on 'fine-tuning containers'. The focus was
things we can do
skype ID brian.kenyon.white
--
bkw
--
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
Shouldn't I be able to have two different nics on a host, on two
different, unrelated, public networks, and have two bridge devices on
the host, and some containers on one bridge and some containers on the
other bridge, and have all containers be able to talk to their
respective internet
On 1/20/2011 10:29 AM, Sergio Daniel Troiano wrote:
Andre,
I'm using Slackware and i've compiled lxc-7.2 because when i tried to
use lxc-7.3 i couldnt mount anything within the container.
You have to create a root enviroment , i use /container, here are all
shared files and directories
On 2/1/2011 5:22 AM, Daniel Lezcano wrote:
Hi All,
The lxc-0.7.4 version will be released very soon.
I suppose most of you are using the version 0.7.3, not the dev version.
Before releasing this new version, I would like to release a pre-version
and that will be very nice if you can check
On 2/2/2011 6:20 AM, Daniel Lezcano wrote:
On 02/02/2011 10:26 AM, Trent W. Buck wrote:
For each lxc.network.type = veth, if you DON'T specify an
lxc.network.hwaddr, you get one assigned at random (example below).
Are these assignments made from a reserved range (a la 169.254/16 in
IPv4), or
On 3/11/2011 10:14 AM, Michael H. Warfield wrote:
On Thu, 2011-03-10 at 19:09 +, Walter Stanish wrote:
... I have read up on the OUI documentation and
looking at the detail on the site LXC could opt for a 32bit OUI which
would
cost $600 for one block. The dev guys might want to setup a
On 3/10/2011 9:04 PM, Stuart Johnson wrote:
Meaning you think python would be too heavyweight?
Certainly as one approaches the embedded end of the spectrum, there's
something to be said for avoiding dependencies on large (compared to
busybox ash) interpreters. It'd be neat if I could deploy
On 3/16/2011 5:11 AM, Geordy Korte wrote:
On Tue, Mar 8, 2011 at 12:42 PM, Stuart Johnson stu...@stu.org.uk
mailto:stu...@stu.org.uk wrote:
maybe just define what you want. Gathering ideas could/would inspire
someone to implement it.
Ideally I want a simple ncurses
On 4/6/2011 4:56 AM, Christoph Mitasch wrote:
Hi,
I'm wondering if anybody is using LXC in a high availability cluster.
I tried to use it in a Pacemaker Cluster together with DRBD.
In theory there would be the VirtualDomain Resource Agent supporting
libvirt. But since my libvirt experience
On 4/6/2011 3:26 PM, l...@zitta.fr wrote:
Hi,
I tried to run an arm container under a x86_64 host and it works
Little how-to :
build a static compiled qemu-arm
take qemu sources and build it with :
./configure --static --target-list=arm-linux-user; make
On 4/6/2011 5:30 PM, Justin Cormack wrote:
On Wed, 2011-04-06 at 16:45 -0400, Brian K. White wrote:
A few questions,
The echo command references /usr/local/bin/qemu-arm, but I don't see
that anywhere else in the recipe. Is that a x86_64 binary on the host or
is that supposed to be a arm
On 4/7/2011 5:23 AM, l...@zitta.fr wrote:
qemu has 2 modes system and user
You described system mode and I used user mode
That resolves a lot of the mystery right there. I hadn't realized qemu
had such a mode.
The other issues are either
* obviated by the fact that you're already doing it
On 4/9/2011 3:00 AM, Ulli Horlacher wrote:
On Wed 2011-04-06 (12:31), Daniel Lezcano wrote:
root@zoo:/lxc# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.0050568e0003 no eth0
is your container up when you show the bridge
.
Geordy Korte
On Fri, Mar 11, 2011 at 11:08 PM, Brian K. White br...@aljex.com
mailto:br...@aljex.com wrote:
On 3/11/2011 10:14 AM, Michael H. Warfield wrote:
On Thu, 2011-03-10 at 19:09 +, Walter Stanish wrote:
... I have read up on the OUI documentation and
looking
On 5/21/2011 7:48 PM, Benjamin Kiessling wrote:
Hi,
Indeed this is not a virtualization specific problem. You want your host to
operate as a router for
the other two IP addresses and, depending on the configuration of OVH,
ARP-Proxy the whole stuff.
Assuming you want have PUB-IP1 on the
On 5/25/2011 7:51 PM, David Touzeau wrote:
Dear all
to detect if we are inside an OpenVZ, openvzve,xen machine
we can check the presence of :
/proc/vz/veinfo
/proc/vz/version
/proc/sys/xen
/sys/bus/xen
/proc/xen
But i did not find any information inside the LXC contener in order to
On 6/2/2011 3:41 PM, Daniel Lezcano wrote:
On 06/02/2011 07:03 PM, Michael H. Warfield wrote:
On Wed, 2011-06-01 at 20:10 -0400, Michael H. Warfield wrote:
On Fri, 2011-05-13 at 22:32 +0200, Daniel Lezcano wrote:
From: Daniel Lezcanodaniel.lezc...@free.fr
We ignore the line of in the
I thought we killed this problem?
nj12:~ # lxc-start -n vps001 -f /etc/lxc/vps001/config
lxc-start: Device or resource busy - failed to remove previous cgroup
'/sys/fs/cgroup/vps001'
lxc-start: failed to spawn 'vps001'
lxc-start: Device or resource busy - failed to remove cgroup
On 6/16/2011 3:26 PM, Serge Hallyn wrote:
Quoting Brian K. White (br...@aljex.com):
I thought we killed this problem?
...
nj12:~ # rm -rf /sys/fs/cgroup/vps001
rmdir
Did that too. no joy.
In fact I did both the main directory and several runs of find|xargs to
delete files and directories
On 6/17/2011 12:06 PM, Serge Hallyn wrote:
Quoting Brian K. White (br...@aljex.com):
On 6/16/2011 3:26 PM, Serge Hallyn wrote:
Quoting Brian K. White (br...@aljex.com):
I thought we killed this problem?
...
nj12:~ # rm -rf /sys/fs/cgroup/vps001
rmdir
Did that too. no joy.
In fact I
On 9/5/2011 12:34 PM, Michael H. Warfield wrote:
On Mon, 2011-09-05 at 09:24 +0200, Papp Tamas wrote:
On 09/05/2011 08:38 AM, Jäkel, Guido wrote:
What is the right way to stop a container?
Dear Papp,
Like with the thread paradigm in computing langugages, the right
way is that the thread
Ideally, for the stated purpose, we need something not named ubuntu.
I already have the same sort of wiki page on opensuse.org since a year
ago but that's of course highly opensuse specific, which is exactly the
problem a central wiki proposes to avoid.
Meanwhile I'm getting less and less in
...@simkowiak.net
On 10/11/2011 06:08 AM, Brian K. White wrote:
That's a pretty substantial reduction. Add it to the possible wish list
along with the MAC address prefix. Sadly I never finished the research
to get that. The $600 is easy, the time to figure out what you're
supposed to do
On 10/17/2011 5:01 PM, Papp Tamas wrote:
On 10/17/2011 10:54 PM, Derek Simkowiak wrote:
/I tried the python script, it just works fine./
Q1: How does the kill -INT init method affect running processes,
especially MySQL and other databases that may need to shutdown
gracefully to avoid data
On 10/19/2011 1:24 PM, Ulli Horlacher wrote:
Besides my problem with cannot stop/kill lxc-start (see other mail), I
have now an even more severe problem: I cannot start ANY container anymore!
I am sure I have overlooked something, but I cannot see what. I am really
desperate now, because this
This isn't meant as an insult but you seem to be trying to do things
backwards and expecting, worse, demanding, a low level tool to contain
high level features that really should be provided by your own
scripting, or by other tools that already exist for that purpose.
If you want to assign
Are you running vsftpd inside the container?
If so, make sure it has these two lines in /etc/vsftpd.conf (in the
container not the host)
# LXC compatibility
# http://www.mail-archive.com/lxc-users@lists.sourceforge.net/msg01110.html
isolate=NO
isolate_network=NO
Do the same for all containers.
On 3/19/2012 9:25 AM, Serge Hallyn wrote:
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
On 03/19/2012 03:50 AM, Serge Hallyn wrote:
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
On 03/19/2012 12:00 AM, Serge Hallyn wrote:
Hi,
Thanks to Jäkel's and Fajar's great ideas, we can now
46 matches
Mail list logo
