From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Cleber Rosa <crosa@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Thomas Huth <thuth@redhat.com>, Warner Losh <imp@bsdimp.com>
Subject: Re: Give the fosshost.org VM a purpose or a retirement
Date: Wed, 24 Nov 2021 15:55:55 +0100 [thread overview]
Message-ID: <cc136013-2632-c149-d258-e2e7f964b07f@redhat.com> (raw)
In-Reply-To: <CA+bd_6JS0t_COHiw2Y3Ej1gAeOGVTScNoS-=Seo+7udAe5wqZw@mail.gmail.com>
On 11/24/21 15:16, Cleber Rosa wrote:
> Hi,
>
> Fosshost.org was kind enough to supply the QEMU project with a public
> VM hosted by them. The original use case we anticipated was to set up
> a GitLab CI runner, because we assumed the VM was KVM capable, but
> that turned out not to be the case.
>
> So, at this point, adding it as a GitLab CI runner would not add any
> significant improvement over the shared runners already provided, and
> it would require more maintenance effort.
>
> If there are any ideas for making use of this resource, and volunteers
> to configure and maintain it, please let me know.
>
> Otherwise, it seems fair to relinquish the resource back to Fosshost.org.
Cc'ing Warner, since for FreeBSD testing we use Cirrus-CI (via
libvirt-ci and have sometime hit GitLab timeout). Series [*]
provides most of what is required to register a FreeBSD runner.
It could be useful to run the user-mode tests.
next prev parent reply other threads:[~2021-11-24 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 14:16 Give the fosshost.org VM a purpose or a retirement Cleber Rosa
2021-11-24 14:33 ` Daniel P. Berrangé
2021-11-24 14:55 ` Philippe Mathieu-Daudé [this message]
2021-11-24 14:56 ` Philippe Mathieu-Daudé
2021-11-25 10:29 ` Warner Losh
2021-11-25 10:35 ` Daniel P. Berrangé
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=cc136013-2632-c149-d258-e2e7f964b07f@redhat.com \
--to=philmd@redhat.com \
--cc=crosa@redhat.com \
--cc=imp@bsdimp.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.