On Wed, May 27, 2015 at 06:26:56PM +0100, Giles Thomas wrote: > Hi Tycho, > > Sorry again for the slow turnaround! > > On 15/05/15 18:59, Tycho Andersen wrote: > >I suspect it still can't find criu and it just isn't finding the binary. > >Can you symlink it into /bin just to be sure? > > That didn't help. However, installing criu from their github repo seems to > have moved things on a bit. Now, instead of getting "error: checkpoint > failed", I get "error: restore failed". Inside /var/log/lxd/migratee, > there is a file called "migration_dump_2015-05-27T17:18:45Z.log", about 536K > long. I've not attached it, as I figure that would be pretty annoying for > everyone else on the list, but I can sent it directly to you if it would be > useful. There is also a 78K lxc.log. > > On the destination machine, there's also a /var/log/lxd/migratee/lxc.log, > which is significantly shorter; here are the contents: > > lxc 1432744458.034 INFO lxc_confile - > confile.c:config_idmap:1390 - read uid map: type u nsid 0 hostid 100000 > range 65536 > lxc 1432744458.034 INFO lxc_confile - > confile.c:config_idmap:1390 - read uid map: type g nsid 0 hostid 100000 > range 65536 > lxc 1432744544.115 INFO lxc_confile - > confile.c:config_idmap:1390 - read uid map: type u nsid 0 hostid 100000 > range 65536 > lxc 1432744544.115 INFO lxc_confile - > confile.c:config_idmap:1390 - read uid map: type g nsid 0 hostid 100000 > range 65536 > lxc 1432744765.397 INFO lxc_confile - > confile.c:config_idmap:1390 - read uid map: type u nsid 0 hostid 100000 > range 65536 > lxc 1432744765.398 INFO lxc_confile - > confile.c:config_idmap:1390 - read uid map: type g nsid 0 hostid 100000 > range 65536 > lxc 1432747103.562 INFO lxc_confile - > confile.c:config_idmap:1390 - read uid map: type u nsid 0 hostid 100000 > range 65536 > lxc 1432747103.563 INFO lxc_confile - > confile.c:config_idmap:1390 - read uid map: type g nsid 0 hostid 100000 > range 65536 > lxc 1432747128.877 ERROR lxc_criu - criu.c:criu_ok:333 - > couldn't find devices.deny = c 5:1 rwm
Ah, this is a sanity check to make sure that various container config properties are set. It looks like things aren't set on the destination host correctly; I think there was a bug with this in the 0.9 client, fixed by 6b5595d03dff7d360f05fa48ee6198d71e7f1ef4, so you may want to upgrade to 0.10. Tycho > > All the best, > > Giles > > -- > Giles Thomas <gi...@pythonanywhere.com> > > PythonAnywhere: Develop and host Python from your browser > <https://www.pythonanywhere.com/> > > A product from PythonAnywhere LLP > 17a Clerkenwell Road, London EC1M 5RD, UK > VAT No.: GB 893 5643 79 > Registered in England and Wales as company number OC378414. > Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK > > _______________________________________________ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
