From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6675131030513385472 X-Received: by 2002:a50:f5bd:: with SMTP id u58mr52602edm.8.1555069058167; Fri, 12 Apr 2019 04:37:38 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a17:906:248c:: with SMTP id e12ls1364980ejb.4.gmail; Fri, 12 Apr 2019 04:37:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqzA7AU52OWgSsDZUuMpXTlD1rKej/y2yG5UWYb+6rswiMLhGVV450Prytrug4uIwk4L1vrp X-Received: by 2002:a17:906:4f0a:: with SMTP id t10mr4734990eju.5.1555069057747; Fri, 12 Apr 2019 04:37:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555069057; cv=none; d=google.com; s=arc-20160816; b=e2vhzBwb4bcx8wcYP24Hwb4G2Rwx4X+KMhXufiIRL8p1+sWCs0u9u54cNtc/lN4Q1S 8vqKB6jxLNUTVHn6U7qtoOdF7LBMguppTn0yW3jk1x8LN8p/WxXfNsxZUn7UVdwztcoL wxJUwSDsLX8crP9y5iDoBv749dMX9AP4vMqMNTifwJAxi7NrUyFzKpo1IaI6c+NxUajw LZz3vxWuzD+cus4IaLK8CdeDNTc6wURzI2ojfmnf8wGyzuwuzt5yRPZFBV/k9fA9++/V IJlQaJ4o4JW/rTYEqIY7a1XAjMzkzfIedAZdh8fJWTNPSQTTetGedQQ2UMc1cxr9aqDE W8LQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=8FnezA9lGtVTw1MA8W0LY80ZzGNj8wMTDEXH4l1PFW4=; b=lXeWYuuXLPp2APb6Yzj/uEaSEtyLsybG0mMjjafpEoPLKWxySCmRV6ruukxcLWNJHt p0jUwBpaeev9R+Y9QUPVvXcj7nJPbhPLARjQaHonyF6od6wwi2D2sN/lkMoM40Pj9aPG QAnfjsC7GfkMs41X5OrkJ7Rb4O5yExVMo2RWhL5HImkGxai5synodRCPy2N5/yegzDAn zlpnajF34rzz3lRLbERHGqqvKwJSs7WDcSZdcvsIxL7SVAh23FHo5X7O4QBONpYy9RfH nPDZb5/GuNKdbvl/QZjrfiwzhGngv6cXpy1fjqro4UUUCDAcftXnJHkAvutbD+rFYLJB DQYA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id j5si1702160ejm.1.2019.04.12.04.37.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Apr 2019 04:37:37 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x3CBbaeA015386 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 12 Apr 2019 13:37:36 +0200 Received: from md1za8fc.ad001.siemens.net ([139.25.68.211]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x3CBban9008444; Fri, 12 Apr 2019 13:37:36 +0200 Date: Fri, 12 Apr 2019 13:37:36 +0200 From: Henning Schild To: "[ext] Jan Kiszka" Cc: , , , Subject: Re: isar error log Message-ID: <20190412133736.5f3b257f@md1za8fc.ad001.siemens.net> In-Reply-To: <74cc4dec-f603-4746-077d-4aae2e20a095@siemens.com> References: <0c1b977d-cd7e-34aa-8d7e-1569b313f75d@siemens.com> <043f0dda-7df0-36d1-c9ae-d9d08d3298d5@siemens.com> <2c3a7bd1-facf-87f2-ec20-2936c893584a@siemens.com> <74cc4dec-f603-4746-077d-4aae2e20a095@siemens.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-TUID: pivZMRF2lUuw Am Thu, 11 Apr 2019 14:42:03 +0200 schrieb "[ext] Jan Kiszka" : > On 11.04.19 12:13, daniel.sangorrin@toshiba.co.jp wrote: > >> -----Original Message----- > >> From: cip-dev-bounces@lists.cip-project.org > >> On Behalf Of > >> daniel.sangorrin@toshiba.co.jp Sent: Thursday, April 11, 2019 7:06 > >> PM To: jan.kiszka@siemens.com > >> Cc: kas-devel@googlegroups.com; isar-users@googlegroups.com; > >> cip-dev@lists.cip-project.org Subject: Re: [cip-dev] isar error log > >> =20 > >>> -----Original Message----- > >>> From: Jan Kiszka > >>> Sent: Thursday, April 11, 2019 6:16 PM > >>> To: sangorrin daniel(=E3=82=B5=E3=83=B3=E3=82=B4=E3=83=AA=E3=83=B3 = =E3=83=80=E3=83=8B=E3=82=A8=E3=83=AB =E2=97=8B=EF=BC=B3=EF=BC=B7=EF=BC=A3= =E2=96=A1=EF=BC=AF=EF=BC=B3=EF=BC=B4) > >>> Cc: > >>> cip-dev@lists.cip-project.org; isar-users@googlegroups.com; > >>> kas-devel@googlegroups.com Subject: Re: isar error log > >>> > >>> On 11.04.19 11:08, daniel.sangorrin@toshiba.co.jp wrote: =20 > >>>>> From: Jan Kiszka > >>>>> On 03.04.19 02:56, daniel.sangorrin@toshiba.co.jp wrote: =20 > >>>>>> Hi Jan, > >>>>>> > >>>>>> Yes I am following the Readme. > >>>>>> > >>>>>> The docker image id for kasproject/kas-isar is 9e9fe44e68d3 (I > >>>>>> am using kas-docker script). And I am =20 > >> using =20 > >>>>> > >>>>> That's the same version I have, and it works for me. > >>>>> =20 > >>>>>> kas-docker --isar build kas.yml:board-qemu-amd64.yml > >>>>>> > >>>>>> Yes, it seems there are multiple errors: > >>>>>> /proc/sys/fs/binfmt_misc/register: Invalid argument > >>>>>> /test-dev-null: Permission denied > >>>>>> > >>>>>> Probably this is a bug or misconfiguration in Ubuntu. I will > >>>>>> try to figure it out.=20 > >>>>> > >>>>> Adding kas-devel: Would be interesting to understand this so > >>>>> that we can fix it or at least document a workaround. Maybe you > >>>>> need to be in some privileged group in order to use privileged > >>>>> docker containers? That's how things work on SUSE. > >>>>> > >>>>> No one around is using Ubuntu, so that distro is likely a blind > >>>>> spot for our testing. =20 > >>>> > >>>> OK, so I figured out that Ubuntu 16.04 was using the service > >>>> "binfmt-support", not "systemd-binfmt". For that reason, the > >>>> "systemd-binfmt" service was inactive. However, "binfmt-support" > >>>> is working fine. I also checked that the post-install script of > >>>> the qemu-user-static package had run correctly and there were > >>>> binfmt configuration files at /var/lib/binfmts/ =20 > >>> > >>> But what prevented the container to tune the host kernel > >>> according to its needs? That is the intended resolution for the > >>> host not having the same settings as the container (or any at > >>> all). =20 > >> > >> To be honest I don't really know what binfmt is all about yet, so > >> I can't even understand what you mean about "tuning the kernel". =20 >=20 > https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html >=20 > >> > >> By the way, I managed to update to the latest Ubuntu 4.4 kernel > >> (145) and the problem persists. I tried to reinstall > >> qemu-user-static etc but still fails humm . > >> Also i just tested on Ubuntu 18.04 and there I can build with ISAR > >> without problems. So I might just leave it unsolved and update to > >> 18.04... =20 > >=20 > > This might be a hint. > > On Ubuntu 18.04 I can see "qemu-alpha" on /proc/sys/fs/binfmt_misc, > > but on Ubuntu 16.04 it isn't there. When running kas-docker, the > > first error is about not being able to > > close /proc/sys/fs/binfmt_misc/register (invalid argument) and the > > second is about qemu-alpha.=20 >=20 > Maybe /proc/sys/fs/binfmt_misc is not mounted into the container > under Ubuntu 16.04, even if that is privileged. Just had a look at a ubuntu 16.04. It does support the fs but it is not mounted. So a pseudo-code patch for the docker entry could be: if not mounted if grep binfmt_misc /proc/filesystems mount else echo "Get a real and recent distro" fi fi Henning > Jan >=20