[CRIU] CRIU LXC

Serge Hallyn serge.hallyn at ubuntu.com
Mon Sep 29 10:27:22 PDT 2014


Thanks I suspect yo'uve helped me narrow down the seach :)

In the meantime reverting commit 2d489f9e87f in the lxc git
tree should fix this for you for now.

Quoting Thouraya TH (thouraya87 at gmail.com):
> root at thouraya-Lenovo-3000-N500:/home/thouraya# uname -a
> Linux thouraya-Lenovo-3000-N500 *3.11.0-15-generic *#25~precise1-Ubuntu SMP
> Thu Jan 30 17:39:31 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> root at thouraya-Lenovo-3000-N500:/home/thouraya# uname -m
> x86_64
> 
> Bests.
> 
> 
> 2014-09-29 15:20 GMT+01:00 Serge Hallyn <serge.hallyn at ubuntu.com>:
> 
> >
> > Are you by chance using a 3.8 kernel?  Dwight reported an identical error
> > with the newest lxc with the 3.8 kernel (which doesn't happen with 3.13,
> > 3.16 or 3.17)
> >
> > Quoting Thouraya TH (thouraya87 at gmail.com):
> > > Thank you for your answer :)
> > > You mean :
> > >
> > > root at thouraya-Lenovo-3000-N500:/home/thouraya# sudo lxc-start -F
> > > --logpriority=DEBUG --logfile=/home/thouraya/file.log -n u1
> > > lxc-start: Permission denied - failed to mount a new instance of
> > '/dev/pts'
> > > lxc-start: failed to setup the new pts instance
> > > lxc-start: failed to setup the container
> > > lxc-start: invalid sequence number 1. expected 2
> > > lxc-start: failed to spawn 'u1'
> > > lxc-start: The container failed to start.
> > > lxc-start: Additional information can be obtained by setting the
> > --logfile
> > > and --logpriority options.
> > >
> > >
> > > ?
> > >
> > >
> > > 2014-09-29 14:43 GMT+01:00 Tycho Andersen <tycho.andersen at canonical.com
> > >:
> > >
> > > > On Mon, Sep 29, 2014 at 12:30:25PM +0100, Thouraya TH wrote:
> > > > > Hello,
> > > > >
> > > > > Please, i try to test this tutorial: http://criu.org/LXC:
> > > > >
> > > > > I followed all instructions, but i have an error message at this
> > command:
> > > > > sudo lxc-start -n u1
> > > > >
> > > > > root at thouraya-Lenovo-3000-N500:~# lxc-start -n u1
> > > > > lxc-start: The container failed to start.
> > > > > lxc-start: To get more details, run the container in foreground mode.
> > > > > lxc-start: Additional information can be obtained by setting the
> > > > --logfile
> > > > > and --logpriority options.
> > > > >
> > > > >
> > > > > Have you an idea please ?
> > > >
> > > > Can you run the container in foreground mode and with the log options
> > > > suggested?
> > > >
> > > > Tycho
> > > >
> > > > > Thanks a lot for help.
> > > > > Best Regards.
> > > >
> > > > > _______________________________________________
> > > > > CRIU mailing list
> > > > > CRIU at openvz.org
> > > > > https://lists.openvz.org/mailman/listinfo/criu
> > > >
> > > >
> >
> > > _______________________________________________
> > > CRIU mailing list
> > > CRIU at openvz.org
> > > https://lists.openvz.org/mailman/listinfo/criu
> >
> >


More information about the CRIU mailing list