From: "Alex Bennée" <alex.bennee@linaro.org>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, riku.voipio@linaro.org
Subject: Re: [Qemu-devel] [PATCH v3 0/5] Support building qemu-user powered docker test images
Date: Fri, 08 Jul 2016 08:53:58 +0100 [thread overview]
Message-ID: <8737nkmup5.fsf@linaro.org> (raw)
In-Reply-To: <20160708061545.GA8848@ad.usersys.redhat.com>
Fam Zheng <famz@redhat.com> writes:
> On Tue, 06/28 16:42, Alex Bennée wrote:
>> This is the latest iteration of my qemu-user support inside Docker.
>> They apply directly on top of master. I've made the changes suggested
>> in the last review and split apart another patch. I've also added a
>> new update command so a tagged image can be updated with the latest
>> QEMU.
>>
>> To use, first ensure you build the debian-bootstrap image:
>>
>> DEB_ARCH=armhf DEB_TYPE=testing \
>> ./tests/docker/docker.py build qemu:debian-bootstrap \
>> ./tests/docker/dockerfiles/debian-bootstrap.docker \
>> --include-executable=./arm-linux-user/qemu-arm
>
> Alex,
>
> Sorry for the late reply.
>
> Is there a way to setup or detect the binfmt_misc configuration on the
> system?
The trick is doing this in a distribution agnostic way. Certainly
Debian-a-like systems have scripts that allow you to query the state of
binmfmt_misc.
> I think it's better to error out (and hint how to fix that) if qemu-arm is not
> registered. Now it only fails complaining about "wrong exec format" after the
> long debootstrap process is done.
Would it be enough to warn if basename of the included executable
doesn't appear anywhere in binfmt_misc?
>
> Fam
>
>>
>> And then run the test quick target:
>>
>> make docker-test-quick@debian-bootstrap J=9 V=1
>>
>> To update the installed QEMU:
>>
>> ./tests/docker/docker.py update qemu:debian-bootstrap \
>> ./arm-linux-user/qemu-arm
>>
>> To run a throwaway container:
>>
>> docker run -t -i --rm qemu:debian-bootstrap
>>
>> I'll leave it up to you how we cleanly integrate multi-arch builds
>> into the Make system ;-)
>>
>> Alex Bennée (5):
>> tests/docker/docker.py: docker_dir outside build
>> tests/docker/docker.py: support --include-executable
>> tests/docker/docker.py: check and run .pre script
>> tests/docker/dockerfiles: new debian-bootstrap.docker
>> tests/docker/docker.py: add update operation
>>
>> tests/docker/docker.py | 144 +++++++++++++++++++++--
>> tests/docker/dockerfiles/debian-bootstrap.docker | 21 ++++
>> tests/docker/dockerfiles/debian-bootstrap.pre | 5 +
>> 3 files changed, 161 insertions(+), 9 deletions(-)
>> create mode 100644 tests/docker/dockerfiles/debian-bootstrap.docker
>> create mode 100755 tests/docker/dockerfiles/debian-bootstrap.pre
>>
>> --
>> 2.7.4
>>
--
Alex Bennée
next prev parent reply other threads:[~2016-07-08 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 15:42 [Qemu-devel] [PATCH v3 0/5] Support building qemu-user powered docker test images Alex Bennée
2016-06-28 15:42 ` [Qemu-devel] [PATCH v3 1/5] tests/docker/docker.py: docker_dir outside build Alex Bennée
2016-06-28 15:42 ` [Qemu-devel] [PATCH v3 2/5] tests/docker/docker.py: support --include-executable Alex Bennée
2016-06-28 15:42 ` [Qemu-devel] [PATCH v3 3/5] tests/docker/docker.py: check and run .pre script Alex Bennée
2016-06-28 15:42 ` [Qemu-devel] [PATCH v3 4/5] tests/docker/dockerfiles: new debian-bootstrap.docker Alex Bennée
2016-06-28 15:42 ` [Qemu-devel] [PATCH v3 5/5] tests/docker/docker.py: add update operation Alex Bennée
2016-07-08 6:15 ` [Qemu-devel] [PATCH v3 0/5] Support building qemu-user powered docker test images Fam Zheng
2016-07-08 7:53 ` Alex Bennée [this message]
2016-07-08 9:14 ` Fam Zheng
2016-07-08 10:10 ` Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737nkmup5.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).