From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, sw@weilnetz.de, jsnow@redhat.com,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [RFC PATCH 0/4] tests: Introducing docker tests
Date: Thu, 4 Feb 2016 12:26:43 +0100 [thread overview]
Message-ID: <56B33573.5070806@redhat.com> (raw)
In-Reply-To: <20160204024334.GG5187@ad.usersys.redhat.com>
On 04/02/2016 03:43, Fam Zheng wrote:
> Non-Linux environments can be sorted out in this framework by pulling
> appropriate 3rd party images from docker hub, assuming there isn't too much
> copyright hassle for Mac OSX and Windows stuff. This is theoretically possible
> because with "--privileged -v /dev/kvm:/dev/kvm": we can spawn a kvm guest
> inside the container. Even without kvm, TCG may also be useful for non-x86
> build env.
>
> This series also covers mingw cross compiling which might catch some windows
> problems.
And especially 32-bit problems. Failing on mingw but not arm32 is rare
overall.
Paolo
prev parent reply other threads:[~2016-02-04 11:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 14:36 [Qemu-devel] [RFC PATCH 0/4] tests: Introducing docker tests Fam Zheng
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 1/4] tests: Introduce Docker based tests Fam Zheng
2016-02-04 11:58 ` Daniel P. Berrange
2016-02-05 6:17 ` Fam Zheng
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 2/4] tests: Add clang docker test Fam Zheng
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 3/4] tests: Add mingw 32/64 cross compiling Fam Zheng
2016-02-03 15:08 ` Stefan Weil
2016-02-04 2:29 ` Fam Zheng
2016-02-04 11:24 ` Paolo Bonzini
2016-02-03 16:14 ` Eric Blake
2016-02-04 2:28 ` Fam Zheng
2016-02-04 12:00 ` Daniel P. Berrange
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 4/4] tests: Add travis container test case Fam Zheng
2016-02-03 15:24 ` [Qemu-devel] [RFC PATCH 0/4] tests: Introducing docker tests Stefan Hajnoczi
2016-02-04 2:43 ` Fam Zheng
2016-02-04 11:26 ` Paolo Bonzini [this message]
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=56B33573.5070806@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).