All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	 Stefan Hajnoczi <stefanha@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	 Peter Maydell <peter.maydell@linaro.org>,
	 Richard Henderson <richard.henderson@linaro.org>,
	 Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: Cirrus CI about to shut down
Date: Mon, 13 Apr 2026 11:47:29 +0100	[thread overview]
Message-ID: <87ldert9vi.fsf@draig.linaro.org> (raw)
In-Reply-To: <adzAhSbs21GGVCUv@redhat.com> ("Daniel P. Berrangé"'s message of "Mon, 13 Apr 2026 11:08:05 +0100")

Daniel P. Berrangé <berrange@redhat.com> writes:

> On Mon, Apr 13, 2026 at 11:04:40AM +0100, Alex Bennée wrote:
>> Thomas Huth <thuth@redhat.com> writes:
>> 
>> > On 12/04/2026 16.28, Stefan Hajnoczi wrote:
>> >> On Sun, Apr 12, 2026, 08:45 Thomas Huth <thuth@redhat.com
>> >> <mailto:thuth@redhat.com>> wrote:
>> >>        Hi,
>> >>     according to https://cirruslabs.org/ <https://cirruslabs.org/> :
>> >>        Cirrus CI will shut down effective Monday, June 1, 2026.
>> >>     I guess that means we have to find an alternative for doing the
>> >> builds on
>> >>     macOS and FreeBSD?
>> >> It may be possible to use QEMU's AWS hosting where we already run
>> >> Linux x86-64 private runners. EC2 can run FreeBSD and Mac instances.
>> >> Sponsorship is on an annual basis though and it would be a shame to
>> >> redo the setup work once AWS sponsorship ends.
>> >> If we decide to use AWS then I can help provide access.
>> >
>> > It seems like gitlab.com also at least features macos runners nowadays:
>> >
>> >  https://docs.gitlab.com/ci/runners/hosted_runners/macos/
>> >
>> > ... however, they are limited to Premium & Ultimate tiers, so the
>> > normal developer cannot use these anymore.
>> >
>> > But since QEMU is part of the "GitLab for Open Source" program, maybe
>> > at least the qemu-project can use these? ... It would be great if one
>> > of the qemu-project Maintainers or Owners could check this! (I only
>> > have the "Reporter" role in the project, so I cannot help here)
>> 
>> Probably - I can have a look and try it out.
>> 
>> Not sure what to do about FreeBSD though. Ideally we want hosted runners
>> so we can exercise the hypervisor (ditto Windows x86 and Arm).
>
> For the various BSDs we have  VMs for QEMU builds, which (in
> theory) we could run from regular gitlab Linux jobs. Running them
> with TCG is rather unpleasant though. Do our private upstream
> runners have nested-virt available to let us use KVM ?

We don't have any custom x86 runners, I have no idea about the cloud
ones that serve the bulk of the CI jobs. I assume the AWS EKS machine
wouldn't by default.

>
>
> With regards,
> Daniel

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2026-04-13 10:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-12 12:43 Cirrus CI about to shut down Thomas Huth
2026-04-12 14:28 ` Stefan Hajnoczi
2026-04-13  7:05   ` Thomas Huth
2026-04-13 10:04     ` Alex Bennée
2026-04-13 10:08       ` Daniel P. Berrangé
2026-04-13 10:47         ` Alex Bennée [this message]
2026-04-13 10:54           ` Mohamed Mediouni

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=87ldert9vi.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.