[CRIU] problem restoring process with alternate rootfs

Tycho Andersen tycho.andersen at canonical.com
Thu Jul 10 07:40:41 PDT 2014


Hi Andrew,

On Thu, Jul 10, 2014 at 06:14:20PM +0400, Andrew Vagin wrote:
> On Thu, Jul 10, 2014 at 08:34:30AM -0500, Tycho Andersen wrote:
> > > What's the command you use for restore? In case tasks live in mount namespace
> > > _and_ chroot (well, pivot_root) the --root option should be used to tell criu
> > > where it is.
> > 
> > My restore command is:
> > 
> > ./criu restore \
> >     -D dump/ \
> >     -vvvvvv \
> >     --file-locks \
> >     --action-script "/home/ubuntu/criu/test/app-emu/lxc/network-script.sh"   \
> >     -n net -n mnt -n ipc -n pid \
> >     --tcp-established \
> >     --root /var/lib/lxc/u1/rootfs \
> > 
> > and now with --root I get:
> > 
> > (00.266014)      1: Path `/var/lib/lxc/u1/rootfs' resolved to `./' mountpoint
> > (00.266017)      1: Error (mount.c:1953): New root and old root are the same
> > 
> > which I also don't understand :(
> 
> Looks like /var/lib/lxc/u1/rootfs isn't a mount point.
> 
> Could you try to bind-mount root in another place and set the new place
> to the --root option?

Ah, I see, that works. Thanks!

Tycho


More information about the CRIU mailing list