Thanks Stephane - Yes, I'd definitely intended to do live migration. I could swear that exact functionality had been working at some point in the past. Glad to know it's not just me.
I'll give your suggestion a try. Jake On Wed, Aug 17, 2016 at 3:16 PM, Stéphane Graber <[email protected]> wrote: > You're making progress, now the two LXD daemons are definitely talking > to each other. You're running into CRIU issues :) > > If you did not intend to do live migration, then stop the source > container and try moving it again. > > If you did intend to use live migration, then there are quite a few > issues still being worked on: > https://launchpad.net/ubuntu/+source/criu/+bugs > > Yours appears to be number 3 on that list. > > You can workaround it by unmounting /sys/kernel/debug/tracing/ and > /sys/kernel/debug/ in your source container. > > On Wed, Aug 17, 2016 at 03:11:38PM -0700, jjs - mainphrame wrote: > > Aw, shucks, it was looking like it might work - but no joy. > > > > root@olympia:~# lxc config set core.https_address 192.168.111.193:8443 > > root@olympia:~# lxc move kangal lxd1: > > error: Error transferring container data: migration restore failed > > (00.192913) 1: Error (mount.c:2406): mnt: Can't mount at > > ./sys/kernel/debug: Invalid argument > > (00.206829) Error (cr-restore.c:1352): 23251 killed by signal 9 > > (00.255466) Error (cr-restore.c:2182): Restoring FAILED. > > > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users >
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
