[CRIU] [Announce] Stable 1.3.1 release

[Tycho Andersen]

Hi Krystof,

On Mon, Sep 15, 2014 at 10:12:31PM +0000, Zmudzinski, Krystof C wrote:
> I'm trying to build a system where I can suspend a container and resume it.  I have tried different things but so far I can only suspend a container using the example on http://criu.org/LXC.
> I can also resume it but it either goes away if I use the -d option with criu restore or it stays there as a child of criu restore without the -d option and lxc-info -n cn says that it is stopped.  This is not optimal since I'd like to use lxc-attach to take a look inside the restored container.
> 
> I used the default LXC package and the 1.1.0-alpha1 with the same results.  Furthermore, lxc-checkpoint in 1.1.0-alpha1 gives me the following errors even when criu dump executed directly succeeds:
> Error (files-reg.c:601): Unaccessible path opened 38:144946, need 2049:2244303

Hmm, this is an error I haven't seen before. Perhaps the criu guys
know more about this?

Tycho

> Error (cr-dump.c:1603): Dump files (pid: 6560) failed with -1
> Error (cr-dump.c:1953): Dumping FAILED.
> 
> I'm willing to try anything but so far, for some reason, I'm not very successful.  
> 
> Krystof
> 
> -----Original Message-----
> From: Tycho Andersen [mailto:tycho.andersen at canonical.com] 
> Sent: Monday, September 15, 2014 3:04 PM
> To: Zmudzinski, Krystof C
> Cc: criu at openvz.org; Pavel Emelyanov
> Subject: Re: [CRIU] [Announce] Stable 1.3.1 release
> 
> Hi Krystof,
> 
> On Mon, Sep 15, 2014 at 06:12:28PM +0000, Zmudzinski, Krystof C wrote:
> > The instructions (http://bazaar.launchpad.net/~tycho-s/+junk/snapshot-instructions/view/head:/README) are not complete or assume that my system is configured in certain way.
> > 
> > First, I had problems with cgroup, then this:
> >       lxc-start 1410804526.880 ERROR    lxc_apparmor - No such file or directory - failed to change apparmor profile to lxc-container-default-with-mounting
> >       lxc-start 1410804526.880 ERROR    lxc_sync - invalid sequence number 1. expected 4
> >       lxc-start 1410804526.880 ERROR    lxc_start - failed to spawn 'u1'
> >       lxc-start 1410804526.880 ERROR    lxc_cgfs - Device or resource busy - cgroup_rmdir: failed to delete /cgroup/lxc/u1-1
> >       lxc-start 1410804531.885 ERROR    lxc_start_ui - The container failed to start.
> >       lxc-start 1410804531.885 ERROR    lxc_start_ui - To get more details, run the container in foreground mode.
> >       lxc-start 1410804531.885 ERROR    lxc_start_ui - Additional information can be obtained by setting the --logfile and --logpriority options.
> >       lxc-start 1410804731.572 ERROR    lxc_cgfs - Could not find writable mount point for cgroup hierarchy 3 while trying to create cgroup.
> >       lxc-start 1410804731.572 ERROR    lxc_start - failed creating cgroups
> >       lxc-start 1410804731.599 ERROR    lxc_start - failed to spawn 'u1'
> >       lxc-start 1410804736.604 ERROR    lxc_start_ui - The container failed to start.
> >       lxc-start 1410804736.604 ERROR    lxc_start_ui - To get more details, run the container in foreground mode.
> >       lxc-start 1410804736.604 ERROR    lxc_start_ui - Additional information can be obtained by setting the --logfile and --logpriority options.
> 
> Hmm, this seems like lxc (or some dependency) is installed incorrectly. Do you happen to have cgroup-lite installed?
> 
> Tycho