Cirrus CI about to shut down

Cirrus CI about to shut down

[Thomas Huth]

  Hi,

according to 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?

  Thomas

Re: Cirrus CI about to shut down

[Stefan Hajnoczi]

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

On Sun, Apr 12, 2026, 08:45 Thomas Huth <thuth@redhat.com> wrote:

>
>   Hi,
>
> according to 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.

Stefan

>

[-- Attachment #2: Type: text/html, Size: 1428 bytes --]

Re: Cirrus CI about to shut down

[Thomas Huth]

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)

  Thomas

Re: Cirrus CI about to shut down

[Alex Bennée]

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).

>
>  Thomas

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro

Re: Cirrus CI about to shut down

[Daniel P. Berrangé]

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 ?


With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|

Re: Cirrus CI about to shut down

[Alex Bennée]

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

Re: Cirrus CI about to shut down

[Mohamed Mediouni]

> On 13. Apr 2026, at 12:47, Alex Bennée <alex.bennee@linaro.org> wrote:
> 
> 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:
>>> 
>>> 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.
Hi,

EKS doesn’t expose nested virtualisation today, only direct EC2 as an opt-in
for *8i instances.

Windows is a bit of an oddball but is supported with the nested virt support
on AWS, but as I’ve been out of sync with that for quite a while can’t tell if
what shipped supports MBEC.