qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Alexander von Gluck IV" <kallisti5@unixzen.com>
Subject: Re: [PATCH] tests/vm/haiku.x86_64: Update the Haiku VM to Beta 4
Date: Mon, 16 Jan 2023 10:13:51 +0100	[thread overview]
Message-ID: <3343fe22-9126-8f22-8a9f-91b9bf169d02@redhat.com> (raw)
In-Reply-To: <20230116083014.55647-1-thuth@redhat.com>

On 16/01/2023 09.30, Thomas Huth wrote:
> The old Haiku VM based on Beta 3 does not work anymore since it
> fails to install the additional packages now that Beta 4 has been
> released. Thanks to Alexander von Gluck IV for providing a new
> image based on Beta 4, we can now upgrade the test image in our
> QEMU CI, too, to get this working again.
> 
> Note that Haiku Beta 4 apparently finally fixed the issue with
> the enumeration of the virtio-block devices (see the ticket at
> https://dev.haiku-os.org/ticket/16512 ) - the tarball disk can
> now be found at index 1 instead of index 0.

I just noticed that we should now remove the related comment, too:

diff a/tests/vm/haiku.x86_64 b/tests/vm/haiku.x86_64
--- a/tests/vm/haiku.x86_64
+++ b/tests/vm/haiku.x86_64
@@ -80,7 +80,6 @@ class HaikuVM(basevm.BaseVM):
          "ninja",
      ]
  
-    # https://dev.haiku-os.org/ticket/16512 virtio disk1 shows up as 0 (reversed order)
      BUILD_SCRIPT = """
          set -e;
          rm -rf /tmp/qemu-test.*



      parent reply	other threads:[~2023-01-16  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16  8:30 [PATCH] tests/vm/haiku.x86_64: Update the Haiku VM to Beta 4 Thomas Huth
2023-01-16  8:59 ` Philippe Mathieu-Daudé
2023-01-16  9:13 ` Thomas Huth [this message]

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=3343fe22-9126-8f22-8a9f-91b9bf169d02@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=kallisti5@unixzen.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).