From: Thomas Huth <thuth@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>,
Richard Zak <richard.j.zak@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Warner Losh <imp@bsdimp.com>
Subject: Re: Qemu on Haiku
Date: Mon, 28 Jun 2021 06:31:47 +0200 [thread overview]
Message-ID: <36125248-9607-197f-453c-b1c75a0fe2e8@redhat.com> (raw)
In-Reply-To: <92ed67e4-777-1361-1217-2b5b708fc15@eik.bme.hu>
On 28/06/2021 02.38, BALATON Zoltan wrote:
> On Sun, 27 Jun 2021, Richard Zak wrote:
>> Hopefully last questions:
[...]
>> 2) Is it acceptable to have a patch for the configure script, or is that
>> generated? I found some Haiku-related issues there
>
> The configure script is not generated, it's just a shell script so you can
> send patches for it I think.
Right, QEMU's "configure" script is handmade.
>> Regarding prior email:
>> Seems like the big tasks are:
>> 1) Haiku VM for continuous integration. Is this hosted in Amazon or other
>> cloud infrastructure?
The QEMU project is using gitlab-CI, Travis-CI and Cirrus-CI, as CI systems
that could be used by everybody. However, most of these are based on
Containers, so it's not possible to run an OS there that is completely
different from the ones that are offered by default.
Now that's where the tests in the tests/vm/ directory come in very handy.
These are based on KVM, so they can run on all Linux hosts that have
virtualization enabled. Thus if the tests/vm/haiku.x86_64 test would work
more properly, it could get run on KVM-enabled machines, too.
>> 3) Supporting aspects of the qemu code relevant to Haiku (found an issue in
>> slirp & configure script)
slirp is a separate project now, if you want to fix something in there,
please report it here:
https://gitlab.freedesktop.org/slirp/libslirp
Thomas
prev parent reply other threads:[~2021-06-28 4:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 4:12 Qemu on Haiku Richard Zak
2021-06-25 7:09 ` Thomas Huth
2021-06-26 2:44 ` Richard Zak
2021-06-26 3:03 ` Warner Losh
2021-06-27 22:27 ` Richard Zak
2021-06-28 0:38 ` BALATON Zoltan
2021-06-28 4:31 ` Thomas Huth [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=36125248-9607-197f-453c-b1c75a0fe2e8@redhat.com \
--to=thuth@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=imp@bsdimp.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.j.zak@gmail.com \
/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).