qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Alexander von Gluck IV" <kallisti5@unixzen.com>,
	"Richard Zak" <richard.j.zak@gmail.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Cleber Rosa" <crosa@redhat.com>
Subject: Re: QEMU's Haiku CI image
Date: Wed, 16 Feb 2022 18:39:53 +0100	[thread overview]
Message-ID: <2af2336b-8a33-1860-5842-95d34263e5fe@redhat.com> (raw)
In-Reply-To: <ea30ad98-8e15-7404-c91c-ec475551b866@amsat.org>

On 16/02/2022 18.16, Philippe Mathieu-Daudé wrote:
> On 16/2/22 17:32, Thomas Huth wrote:
>> On 16/02/2022 16.52, Alexander von Gluck IV wrote:
>>> February 16, 2022 6:31 AM, "Thomas Huth" <thuth@redhat.com> wrote:
>>>>
>>>> while researching the different "sed" options on our supported build 
>>>> platform today, I started
>>>> "make vm-build-haiku.x86_64" in my QEMU build directory for the first 
>>>> time since many months again.
>>>> And I had to discover that this is completely out of date. The image 
>>>> does not contain any version
>>>> of Python 3 yet which we require for compilation since more than a year 
>>>> now already, and the Haiku
>>>> version in there seems to be too old to do a "pkgman install -y python3" 
>>>> ... so this has been
>>>> completely been bitrotting since more than a year now. Is anybody still 
>>>> interested in keeping the
>>>> Haiku support in QEMU? If so, please help to get the VM image updated. 
>>>> Thanks!
>>>
>>> I submitted
>>> https://patchwork.kernel.org/project/qemu-devel/patch/20220216154208.2985103-1-kallisti5@unixzen.com/ 
>>>
>>> to fix this issue.  The build runs as expected after that patchset.
>>>
>>> Likely cause is us no longer packing a "python" binary, deferring to 
>>> "python2" vs "python3"
>>>
>>> I'm still the most likely maintainer.  Are there still plans to automate 
>>> the tests for Haiku to
>>> prevent this from happening again in the future?
>>
>> AFAIK we still don't have a machine where we could properly run VM-based 
>> tests in the CI, do we? Peter? Cleber?
> 
> We still have unused fosshost.org resources. What we don't have is a
> sysadmin willing to install the VM and maintain it over time.

I thought that one does not have KVM enabled?

  Thomas




  reply	other threads:[~2022-02-16 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 12:31 QEMU's Haiku CI image Thomas Huth
2022-02-16 15:52 ` Alexander von Gluck IV
2022-02-16 16:32   ` Thomas Huth
2022-02-16 17:16     ` Philippe Mathieu-Daudé via
2022-02-16 17:39       ` Thomas Huth [this message]
2022-02-16 19:21       ` Daniel P. Berrangé
2022-02-17  7:31         ` Thomas Huth

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=2af2336b-8a33-1860-5842-95d34263e5fe@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=kallisti5@unixzen.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=richard.j.zak@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).