qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting rid of the last bits of QEMU's 'ad-hoc CI' for merges


From: Stefan Hajnoczi
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

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: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]