[lxc-users] lxc progress and a few questions

[jjs - mainphrame]

I've looked at ct migration between 2 ubuntu 16.04 hosts today, and had
some interesting problems;  I find that migration of stopped containers
works fairly reliably; but live migration, well, it transfers a lot of
data, then exits with a failure message. I can then move the same
container, stopped, with no problem.

The error is the same every time, a failure of "mkdtemp" -


root at ronnie:~# lxc move third lxd:
error: Error transferring container data: restore failed:
(00.033172)      1: Error (cr-restore.c:1489): mkdtemp failed
crtools-proc.x9p5OH: Permission denied
(00.060072) Error (cr-restore.c:1352): 9188 killed by signal 9
(00.117126) Error (cr-restore.c:2182): Restoring FAILED.

root at raskolnikov:~# lxc move third lxd2:
error: Error transferring container data: restore failed:
(00.039099)      1: Error (cr-restore.c:1489): mkdtemp failed
crtools-proc.a3U2t5: Permission denied
(00.063015) Error (cr-restore.c:1352): 1771 killed by signal 9
(00.115261) Error (cr-restore.c:2182): Restoring FAILED.

root at ronnie:~# lxc move third lxd:
error: Error transferring container data: restore failed:
(00.034542)      1: Error (cr-restore.c:1489): mkdtemp failed
crtools-proc.gee5YS: Permission denied
(00.059955) Error (cr-restore.c:1352): 9274 killed by signal 9
(00.109272) Error (cr-restore.c:2182): Restoring FAILED.


Thanks for any pointers you can provide -

PS  - on a side note, I'd originally set up the new box with a separate
/var partition on btrfs. As a result, "criu check" would die instantly with
a segmentation error. After putting /var back on / (ext4) criu check
produces the message "Looks good."

Jake



On Mon, Mar 28, 2016 at 7:47 AM, Tycho Andersen <
tycho.andersen at canonical.com> wrote:

> On Sun, Mar 27, 2016 at 09:22:44PM -0700, jjs - mainphrame wrote:
> > You've had some success with live migrations? At any rate, I'm upgrading
> my
> > ubuntu 15.10 test box to 16.04 so that I'll have 2 of them. I'll give it
> a
> > whirl.
>
> Yes, there are still various unsupported kernel features, but it
> should work out of the box for a modern stock xenial image on a xenial
> host. There is one more xenial kernel patch which will eventually be
> released that will break things, but I'm in the process of upstreaming
> some CRIU patches to handle that case, and we'll distro patch those
> when they're ready.
>
> Tycho
>
> > On Sun, Mar 27, 2016 at 9:20 PM, Fajar A. Nugraha <list at fajar.net>
> wrote:
> >
> > > On Sun, Mar 27, 2016 at 11:31 PM, jjs - mainphrame <jjs at mainphrame.com
> >
> > > wrote:
> > > > The 2nd link you sent seems to indicate that
> > > > live migration wants to work, but I haven't been able to find any
> reports
> > > > from normal users in the field who've actually succeeded with live
> > > > migration. if I've missed something, please let me know.
> > >
> > > My best advice is to try yourself with latest 16.04 daily.
> > >
> > > I've had both success and failure with it.
> > >
> > > --
> > > Fajar
> > > _______________________________________________
> > > lxc-users mailing list
> > > lxc-users at lists.linuxcontainers.org
> > > http://lists.linuxcontainers.org/listinfo/lxc-users
> > >
>
> > _______________________________________________
> > lxc-users mailing list
> > lxc-users at lists.linuxcontainers.org
> > http://lists.linuxcontainers.org/listinfo/lxc-users
>
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20160328/55ab1383/attachment-0001.html>