[CRIU] about checkpointing lxc container

Cyrill Gorcunov gorcunov at gmail.com
Thu Oct 10 09:42:08 PDT 2013


On Thu, Oct 10, 2013 at 08:54:50AM -0400, Xinyang Ge wrote:
> > It means there is some socket in container which we don't support yet
> > (maybe raw sockets or something). Try to play with "ss" utility inside
> > container to figure out which sockets are present there.
> >
> > Also, you may start "criu dump" with -v4 option and post the output
> > here, as far as I remember we collect information about sockets
> > and print it.
> 
> I figured out it was udev that caused obstacles from checkpointing. I
> stopped it and another error occurs:
> 
> (00.093895) Error (tty.c:221): tty: Unexpected format on path /dev/lxc/tty4
> 
> I attached the -v4 output in this email. Could you please take a look
> and give us some suggestions on how to handle it?

We can handle /dev/ptmx and /dev/pts/N, where N is a number of slave
terminal point. That said lxc seems to use terminals which we don't
handle yet. Is there a chance to get rid of them (sorry I'm not really
familiar with lxc internals)?


More information about the CRIU mailing list