[CRIU] CRIU and travis (aarch64)
Adrian Reber
adrian at lisas.de
Wed Oct 30 00:08:53 MSK 2019
On Tue, Oct 29, 2019 at 10:01:40AM -0700, Andrei Vagin wrote:
> Hi Adrian,
>
> On Tue, Oct 29, 2019 at 9:26 AM Adrian Reber <adrian at lisas.de> wrote:
> >
> > I just tried to switch CRIU to use the native aarch64 support on Travis
> > and it failed with:
>
> I was playing with this too:
> https://travis-ci.org/avagin/criu/jobs/594911849
Ha, that looks more or less just the same to my changes.
> but I don't have time to complete this, so it would be nice if you
> will be able to send patches:
I can try to look more into it, no problem.
> > + [ -f ]
> > + umask 0000
> > + ./criu/criu check
> > Error (criu/cr-check.c:512): /proc/sys/kernel/sem_next_id is inaccessible: Permission denied
> >
> > As I have been told this is related to the fact that Travis uses
> > unprivileged LXD containers to distribute jobs to aarch64. As I
> > understand it this makes it probably not possible for us to use Travis's
> > native aarch64 support.
> >
> > Let me know if anyone has an idea if this can be solved somehow.
>
> We can try to dump and restore env00 as regular user:
> zdtm.py run zdtm/static/env00 --user
Let me try that. Thanks.
Adrian
More information about the CRIU
mailing list