From: Stefan Hajnoczi <stefanha@redhat.com>
To: Cleber Rosa <crosa@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: Getting rid of the last bits of QEMU's 'ad-hoc CI' for merges
Date: Mon, 16 May 2022 16:25:05 +0100 [thread overview]
Message-ID: <YoJs0SmcohJxlh9y@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAFEAcA_5ouMzMx=1da0VFHXWvMsOoYJ_zZCA6Q_LjwNNO4WwOQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
On Mon, May 16, 2022 at 03:35:25PM +0100, Peter Maydell wrote:
> On Mon, 16 May 2022 at 15:30, Thomas Huth <thuth@redhat.com> wrote:
> >
> > On 16/05/2022 14.43, Peter Maydell wrote:
> > > For the BSDs, the ad-hoc CI is just running the tests/vm
> > > "make vm-build-netbsd" etc. Is there some way we can get
> > > coverage of this into the gitlab CI setup? (I think we
> > > have FreeBSD via Cirrus CI, so I have not listed that one.)
> >
> > A simple setup is already there, running NetBSD and OpenBSD via KVM on the
> > Cirrus-CI, see e.g.:
> >
> > https://gitlab.com/thuth/qemu/-/jobs/2411943817#L1973
> >
> > Caveats:
> > - The jobs are currently marked as "manual only" since the double
> > indirect setup (via cirrus-run and KVM) is not that reliable.
> > Also we can not run that many cirrus-ci jobs in parallel, so
> > we likely don't want to enable these by default.
> > - Compilation is not very fast, the jobs often run longer than
> > 1h, though the --target-list is very short already.
> >
> > Anyway, this should show that running NetBSD and OpenBSD is very well
> > possible in our CI - we just need a more powerful x86 host with KVM enabled
> > for this.
>
> Yes, if we have an x86 machine we can use as a private CI runner
> for these jobs that would work.
Hi Cleber,
I think there was a Fosshost x86 machine that is currently idle? Does it
support nested virt?
Thanks,
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-05-16 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 12:43 Getting rid of the last bits of QEMU's 'ad-hoc CI' for merges Peter Maydell
2022-05-16 13:51 ` Cédric Le Goater
2022-05-16 13:55 ` Peter Maydell
2022-05-16 14:50 ` Cédric Le Goater
2022-05-16 15:58 ` Daniel P. Berrangé
2022-05-16 14:26 ` Paolo Bonzini
2022-05-16 14:30 ` Thomas Huth
2022-05-16 14:35 ` Peter Maydell
2022-05-16 15:25 ` Stefan Hajnoczi [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=YoJs0SmcohJxlh9y@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=danielhb413@gmail.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.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).