From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sukadev Bhattiprolu Subject: Re: [RFC][PATCH 0/5][lxc]: Link with USERCR Date: Wed, 24 Mar 2010 12:47:44 -0700 Message-ID: <20100324194744.GC20031@us.ibm.com> References: <20100319063912.GA25732@us.ibm.com> <4BA7826D.10706@fr.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4BA7826D.10706-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Daniel Lezcano Cc: Containers , clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org List-Id: containers.vger.kernel.org Daniel Lezcano [dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org] wrote: > Sukadev Bhattiprolu wrote: >> Link lxc_checkpoint, lxc_restart with USERCR[2] >> > >> 3. Checkpoint/restart a simple LXC container >> >> $ lxc-execute --name foo --rcfile lxc-no-netns.conf -- /bin/sleep 1000 >> >> $ lxc-freeze --name foo >> >> $ lxc-checkpoint --name foo --image /root/lxc-foo.ckpt >> >> $ lxc-unfreeze --name foo > > IMO, the freeze / thaw should be done in the lxc_checkpoint function code. Well, by separating the freeze and checkpoint, we could do things like snapshot the filesystem or would lxc_checkpoint make an external call to do that ? I will leave it as is for my next version and I am guessing it can be done easily later ? > >> $ lxc-stop --name foo >> >> $ lxc-restart --name foo --image /root/lxc-foo.ckpt > > Is the container restarted in a frozen state ? It can be (by setting the restart_args->freezer). I will leave it in frozen for now. Maybe later we can add a command line option to let user choose whether or not to leave it frozen