From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6675131030513385472 X-Received: by 2002:ac2:491c:: with SMTP id n28mr2431506lfi.4.1554986527935; Thu, 11 Apr 2019 05:42:07 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:998e:: with SMTP id w14ls660502lji.14.gmail; Thu, 11 Apr 2019 05:42:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqxwI5SHCZHfTIStG0nISSfSeQyXR2wDc4rIawN3TmUJbtFLNS8RID6gzdBamt3m1zZ3TJaF X-Received: by 2002:a2e:3015:: with SMTP id w21mr2661224ljw.20.1554986527350; Thu, 11 Apr 2019 05:42:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554986527; cv=none; d=google.com; s=arc-20160816; b=RVhQQfIhDjB3RW5znmNL0h7QhN9tK04jqrfVbXrXpBgBAkoiE41KVlJxJEPWuig3fE IzjUDTBeHRhNtYhrDPUlfpPiMN4Ah5h2Mkgc2KU8hxBxyYlCSt34e7okz5nmHr1Gf0A9 mABZnjagURKs0HI/GU7eSRYkHEB/LipPp5B9THXc797MGYAxXiEFb75T3FoTQR1ujW30 031L0ZZDkitriCRnR4pRMpyUk04qCD3jAx4z2Yb6JKsPUMlIJUGzLspjlX98s3vrlnBy Enn2xsmwZj+AG7LF02HQL95DLtJFa5spbcFSxD92uR6Z12gTTn3XsYI72D/v0MkTN5md rtmw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject; bh=5Vkn58DByfsHS4XtfSE0kaTLgCs2mCkssoCNMu98k9M=; b=iclcpA8lU722eear5SXSuA5OKLZBSaSW1aBg6l1iYzpdMitxPBIU8OCF5mmLF8jpPe aTFhpFc0fN5UpeTOGQzz18pn1W4hl963sJUc6H9x6GLlJxlANiWoEjCGG+WsE1CFNEmU W3aNzScdfBuXPCemQgulN8Y0QaToRJ0GVkm7h+mGjbX1sCnM9rqdS2YbmuFpn8LX1LAD 3bBmEInzvAyKyOdWGErrulrpUd8YB6i8aMd6yZEXixgF9FwW55JPdnXe+cSWHQuVub5y 8JJ4F88C0LDeZqp+KgpO64MVivNs633V1a5x413ZV/HSqy85ED/Zk7N9YupPi3mMFp/c eKzw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id q66si1244855lje.2.2019.04.11.05.42.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Apr 2019 05:42:07 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@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 jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@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 x3BCg5cw008441 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 11 Apr 2019 14:42:06 +0200 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x3BCg5gx030475; Thu, 11 Apr 2019 14:42:05 +0200 Subject: Re: isar error log To: daniel.sangorrin@toshiba.co.jp Cc: kas-devel@googlegroups.com, isar-users@googlegroups.com, cip-dev@lists.cip-project.org References: <0c1b977d-cd7e-34aa-8d7e-1569b313f75d@siemens.com> <043f0dda-7df0-36d1-c9ae-d9d08d3298d5@siemens.com> <2c3a7bd1-facf-87f2-ec20-2936c893584a@siemens.com> From: Jan Kiszka Message-ID: <74cc4dec-f603-4746-077d-4aae2e20a095@siemens.com> Date: Thu, 11 Apr 2019 14:42:03 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: oTw+F0FnrvAz 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 >> >>> -----Original Message----- >>> From: Jan Kiszka >>> Sent: Thursday, April 11, 2019 6:16 PM >>> To: sangorrin daniel(サンゴリン ダニエル ○ＳＷＣ□ＯＳＴ) >>> 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: >>>>> From: Jan Kiszka >>>>> On 03.04.19 02:56, daniel.sangorrin@toshiba.co.jp wrote: >>>>>> 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 >> using >>>>> >>>>> That's the same version I have, and it works for me. >>>>> >>>>>> 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. >>>>>> >>>>> >>>>> 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. >>>> >>>> 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/ >>> >>> 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). >> >> 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". https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html >> >> 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... > > 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. > Maybe /proc/sys/fs/binfmt_misc is not mounted into the container under Ubuntu 16.04, even if that is privileged. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux