[Bug 1580765] Re: Need support for rewriting mount sources
With the same nodes fully updated (kernel 4.4.0-53, lxd 2.0.8, criu 2.6-1ubuntu1~ubuntu16.04.2), I find that live migration now works - yay! Note: this is only if I don't change the container name. If I do (e.g. "lxc move sample nuc1:foobar") then I get: error: migration restore failed (00.059324) Warn (criu/apparmor.c:421): apparmor namespace /sys/kernel/security/apparmor/policy/namespaces/lxd-sample_ already exists, restoring into it (00.063180) Warn (criu/cr-restore.c:853): Set CLONE_PARENT | CLONE_NEWPID but it might cause restore problem,because not all kernels support such clone flags combinations! (00.168620) 1: Warn (criu/autofs.c:77): Failed to find pipe_ino option (old kernel?) (00.182952) 1: Error (criu/mount.c:2517): mnt: Can't mount at ./dev/.lxd-mounts: No such file or directory (00.201952) Error (criu/cr-restore.c:1024): 5637 killed by signal 9: Killed (00.230527) Error (criu/cr-restore.c:1890): Restoring FAILED. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580765 Title: Need support for rewriting mount sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/criu/+bug/1580765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580765] Re: Need support for rewriting mount sources
Hi, I believe: https://github.com/lxc/lxc/pull/1266 and https://lists.openvz.org/pipermail/criu/2016-October/032680.html will fix this, without the need for rewriting mount sources in CRIU itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580765 Title: Need support for rewriting mount sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/criu/+bug/1580765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580765] Re: Need support for rewriting mount sources
That sounds a plausible reason. Preventing change of target name when migrating a running container would be a reasonable temporary solution. So I retried, this time keeping the target container name the same. However it failed again, but with a different error: root@nuc1:~# lxc move sample nuc2:sample error: Error transferring container data: restore failed: (00.213976) 1: Error (mount.c:2406): mnt: Can't mount at ./sys/kernel/debug: Invalid argument (00.229795) Error (cr-restore.c:1352): 4333 killed by signal 9 (00.272166) Error (cr-restore.c:2182): Restoring FAILED. Running again with inotifywait on the target: root@nuc2:~# inotifywait -mr /var/lib/lxd/shmounts Setting up watches. Beware: since -r was given, this may take a while! Watches established. /var/lib/lxd/shmounts/ CREATE,ISDIR sample /var/lib/lxd/shmounts/ OPEN,ISDIR sample /var/lib/lxd/shmounts/ ACCESS,ISDIR sample /var/lib/lxd/shmounts/ CLOSE_NOWRITE,CLOSE,ISDIR sample /var/lib/lxd/shmounts/sample/ DELETE_SELF /var/lib/lxd/shmounts/ DELETE,ISDIR sample Let me know if you want this opening as a separate issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580765 Title: Need support for rewriting mount sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/criu/+bug/1580765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
