[CRIU] Trying to Checkpoint LXC

[Nipun Arora]

Hi all,

Thanks for the assist, I still seem to be having problems. Is there any
other specific configuration flags I need to be aware of ?
Even with the lxc.console = none in the config still seem to have some
issues.

Here is the dump.log attached...

Thanks
Nipun


On Sun, Nov 24, 2013 at 2:21 PM, Andrew Vagin <avagin at parallels.com> wrote:

> On Sun, Nov 24, 2013 at 12:16:31AM +0400, Pavel Emelyanov wrote:
> > On 11/23/2013 01:35 AM, Nipun Arora wrote:
> > > (02.773070) tty: Dumping tty 68 with id 0x158
> > > (02.773214) Error (tty.c:221): tty: Unexpected format on path
> /dev/lxc/tty4
> > > (02.773278) ----------------------------------------
> >
> >
> > That's the reason of failure. If I'm not mistaken, this is an external
> console
> > of the container. We haven't looked at supporting such containers yet
> (we don't
> > create such when we start OpenVZ containers).
> >
> > If you can configure your container not to create this thing, dump should
> > proceed.
>
> http://criu.org/LXC
>
> You can add "lxc.console=none" in a container config.
>
> > Another option could be to tune the tty.c file to detect LXC consoles
> > and dump them as such (most of the code should be there, we just need the
> > proper detection and a mark in the image file, that this thing is an LXC
> > console).
> >
> > Thanks,
> > Pavel
> > _______________________________________________
> > CRIU mailing list
> > CRIU at openvz.org
> > https://lists.openvz.org/mailman/listinfo/criu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20131129/e3febe2b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dump.log
Type: application/octet-stream
Size: 72238 bytes
Desc: not available
URL: <http://lists.openvz.org/pipermail/criu/attachments/20131129/e3febe2b/attachment-0001.obj>