From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Boddie Subject: Re: Bootstrapping on a new platform Date: Mon, 11 Dec 2017 17:36:09 +0100 Message-ID: <201712111736.12484.paul@boddie.org.uk> References: <201712030017.19982.paul@boddie.org.uk> <201712081719.15396.paul@boddie.org.uk> <87609d34rn.fsf@gnu.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55883) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eOR4G-0005E0-Uc for help-guix@gnu.org; Mon, 11 Dec 2017 11:36:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eOR4E-0005Ch-CV for help-guix@gnu.org; Mon, 11 Dec 2017 11:36:36 -0500 In-Reply-To: <87609d34rn.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ludovic =?utf-8?q?Court=C3=A8s?= Cc: help-guix@gnu.org On Monday 11. December 2017 12.03.56 Ludovic Court=C3=A8s wrote: >=20 > Paul Boddie skribis: > > This resembling what I showed before. Meanwhile in the child process log > > (/tmp/guix.797) the clone call with EINVAL is this one: > >=20 > > clone(child_stack=3D0xbffedfa4, > > flags=3DCLONE_NEWNS|CLONE_NEWUTS|CLONE_NEWIPC| > > CLONE_NEWPID|CLONE_NEWNET|SIGCHLD) =3D -1 EINVAL (Invalid argument) > >=20 > > Again, this is using the 4.9.67 kernel. >=20 > This suggests that namespaces are not fully supported with this kernel. > The clone(2) page has this: >=20 > EINVAL CLONE_NEWIPC was specified in flags, but the kernel was not > configured with the CONFIG_SYSVIPC and CONFIG_IPC_NS options. >=20 > EINVAL CLONE_NEWNET was specified in flags, but the kernel was not=20 > configured with the CONFIG_NET_NS option. >=20 > EINVAL CLONE_NEWPID was specified in flags, but the kernel was n= ot > configured with the CONFIG_PID_NS option. >=20 > EINVAL CLONE_NEWUTS was specified in flags, but the kernel was not > configured with the CONFIG_UTS option. >=20 > Could it be one of these? I ran "make menuconfig ARCH=3Dum" and saw that "User namespace" and "PID=20 Namespaces" were not enabled. So I enabled them, rebuilt the kernel, and th= en=20 ran the User Mode Linux instance again. This time, it would appear that running the daemon and then running a build= =20 command gets the daemon to do some work. There have been some problems with= =20 hashes, as reported before, but the problem with clone seems to have been=20 solved. Sorry for the noise, but I guess this is what happens when someone tries to= do=20 things the hard way. Thanks for identifying the cause of the problem! Paul