* Cirrus CI about to shut down @ 2026-04-12 12:43 Thomas Huth 2026-04-12 14:28 ` Stefan Hajnoczi 0 siblings, 1 reply; 7+ messages in thread From: Thomas Huth @ 2026-04-12 12:43 UTC (permalink / raw) To: QEMU Developers Cc: Peter Maydell, Alex Bennée, Richard Henderson, Stefan Hajnoczi, Daniel P. Berrange 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Cirrus CI about to shut down 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 0 siblings, 1 reply; 7+ messages in thread From: Stefan Hajnoczi @ 2026-04-12 14:28 UTC (permalink / raw) To: Thomas Huth Cc: QEMU Developers, Peter Maydell, Alex Bennée, Richard Henderson, Stefan Hajnoczi, Daniel P. Berrange [-- 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 --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Cirrus CI about to shut down 2026-04-12 14:28 ` Stefan Hajnoczi @ 2026-04-13 7:05 ` Thomas Huth 2026-04-13 10:04 ` Alex Bennée 0 siblings, 1 reply; 7+ messages in thread From: Thomas Huth @ 2026-04-13 7:05 UTC (permalink / raw) To: Stefan Hajnoczi Cc: QEMU Developers, Peter Maydell, Alex Bennée, Richard Henderson, Stefan Hajnoczi, Daniel P. Berrange 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Cirrus CI about to shut down 2026-04-13 7:05 ` Thomas Huth @ 2026-04-13 10:04 ` Alex Bennée 2026-04-13 10:08 ` Daniel P. Berrangé 0 siblings, 1 reply; 7+ messages in thread From: Alex Bennée @ 2026-04-13 10:04 UTC (permalink / raw) To: Thomas Huth Cc: Stefan Hajnoczi, QEMU Developers, Peter Maydell, Richard Henderson, Stefan Hajnoczi, Daniel P. Berrange 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Cirrus CI about to shut down 2026-04-13 10:04 ` Alex Bennée @ 2026-04-13 10:08 ` Daniel P. Berrangé 2026-04-13 10:47 ` Alex Bennée 0 siblings, 1 reply; 7+ messages in thread From: Daniel P. Berrangé @ 2026-04-13 10:08 UTC (permalink / raw) To: Alex Bennée Cc: Thomas Huth, Stefan Hajnoczi, QEMU Developers, Peter Maydell, Richard Henderson, Stefan Hajnoczi 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 :| ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Cirrus CI about to shut down 2026-04-13 10:08 ` Daniel P. Berrangé @ 2026-04-13 10:47 ` Alex Bennée 2026-04-13 10:54 ` Mohamed Mediouni 0 siblings, 1 reply; 7+ messages in thread From: Alex Bennée @ 2026-04-13 10:47 UTC (permalink / raw) To: Daniel P. Berrangé Cc: Thomas Huth, Stefan Hajnoczi, QEMU Developers, Peter Maydell, Richard Henderson, Stefan Hajnoczi 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Cirrus CI about to shut down 2026-04-13 10:47 ` Alex Bennée @ 2026-04-13 10:54 ` Mohamed Mediouni 0 siblings, 0 replies; 7+ messages in thread From: Mohamed Mediouni @ 2026-04-13 10:54 UTC (permalink / raw) To: Alex Bennée Cc: "Daniel P. Berrangé", Thomas Huth, Stefan Hajnoczi, QEMU Developers, Peter Maydell, Richard Henderson, Stefan Hajnoczi > 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. ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2026-04-13 10:55 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2026-04-13 10:54 ` Mohamed Mediouni
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.