Re: [Lxc-users] Live Migration of LXC
On 10/24/2011 02:07 PM, Ulli Horlacher wrote: On Mon 2011-10-24 (12:03), Greg Kurz wrote: C/R and live migration is a complicated matter for LXC containers. I have assumed nothing else... Give BLCR a try : https://ftg.lbl.gov/CheckpointRestart/CheckpointDownloads.html It doesn't require a kernel patch, although it's clearly peeking and poking with the kernel internals. O.8.4 builds smoothly on debian, f14, and 2.6.38. I don't think it would be too complex to hook BLCR in C/R backend available in lxc. No status for the moment... I guess people who really want migration should participate Not every LXC (admin-)user is a kernel hacker, too. I am fluent in Perl programming, but not in C. at least to show kernel maintainers there's a demand for it. How can we do this? Send mass e-mails (spam) to the kernel maintainers? :-) That has been done already. Cheers, C. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] /proc/process id/ns is not found
On 11/04/2011 03:37 PM, Dong-In David Kang wrote: I could build Linux 2.6.83.2 with lxc patches. I could make lxc-0.7.4 work with it. (lxc-0.7.5 did not work.) I mean it doesn't complain any more. However, I'm not sure if it really works. I did the follwoing: $ lxc-attach -n foo -- /bin/cat /etc/fstab But it shows host's /etc/fstab (not foo's /etc/fstab). I did a few other things. But the outputs are the host's (not the container's). what about : $ lxc-attach -n foo -- ps -ef --forest C. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] what's the difference in lxc-attach
On 04/07/2011 07:46 AM, Ramez Hanna wrote: from a post that i found earlier in the archive subject entering a container by Daniel Lezcano i cannot see the differece between lxc-attach and lxc-execute could someone explain? lxc-execute creates a container and exec's a command/application inside it (see manual). lxc-attach enters a *running* container and exec's a command inside it (manual soon to come). This ability of creating an exogenous process inside a container requires a kernel patchset. C. -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Lxc-attach status update?
On 03/31/2011 12:04 PM, Goran Cetusic wrote: I noticed there is no man page on Debian for lxc-attach. Since lxc-attach is of great use to me I would like to write it if nobody minds. I was going to do it but please do, btw, -- is not documented in lxc-execute.1 C. -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] lxc-attach setns patch for kernel 2.6.34
On 07/28/2010 10:41 AM, Sebastien Pahl wrote: Hi, I'm trying to adapt the patch for lxc-attach to 2.6.34. A few hunks fail but they are trivial to fix. There is only one where I'm not sure: -- Index: 2.6.33/kernel/cgroup.c === --- 2.6.33.orig/kernel/cgroup.c +++ 2.6.33/kernel/cgroup.c @@ -2453,7 +2453,7 @@ static struct cgroup_pidlist *cgroup_pid { struct cgroup_pidlist *l; /* don't need task_nsproxy() if we're looking at ourself */ - struct pid_namespace *ns = get_pid_ns(current-nsproxy-pid_ns); + struct pid_namespace *ns = get_pid_ns(task_active_pid_ns(current)); /* * We can't drop the pidlist_mutex before taking the l-mutex in case * the last ref-holder is trying to remove l from the list at the same -- The kernel/cgroup.c file has changed: Instead of: struct pid_namespace *ns = get_pid_ns(current-nsproxy-pid_ns); now there is: struct pid_namespace *ns = current-nsproxy-pid_ns; From what I have seen in the rest of the code I assume I can just replace it by this line: struct pid_namespace *ns = task_active_pid_ns(current); Am I correct in my assumptions? yes. here's our patch for 2.6.34 we should be pushing this patchset to mainline kernel. Did Eric plan to do so ? cheers, C. index 6d870f2..0a2e55e 100644 --- a/kernel/cgroup.c +++ b/kernel/cgroup.c @@ -2650,7 +2650,7 @@ static struct cgroup_pidlist *cgroup_pidlist_find(struct cgroup *cgrp, { struct cgroup_pidlist *l; /* don't need task_nsproxy() if we're looking at ourself */ - struct pid_namespace *ns = current-nsproxy-pid_ns; + struct pid_namespace *ns = task_active_pid_ns(current); /* * We can't drop the pidlist_mutex before taking the l-mutex in case -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users