From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PULL 0/2] Seabios 1.17.0 20250611 patches
Date: Thu, 12 Jun 2025 08:59:58 -0400 [thread overview]
Message-ID: <CAJSP0QXFX9QBCu3h_Od1YeqTnB7gOUKRQ8ipnyKGxtY29kGA_A@mail.gmail.com> (raw)
In-Reply-To: <aEqo-1g4gL0QXKWe@redhat.com>
On Thu, Jun 12, 2025 at 6:16 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> On Wed, Jun 11, 2025 at 03:21:38PM -0400, Stefan Hajnoczi wrote:
> > On Wed, Jun 11, 2025 at 2:03 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
> > >
> > > FYI, this seabios 1.17.0 release appears to have broken the
> > > ability to use virtio-pci with libguestfs+QEMU:
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2372329
> > >
> > > so I'd suggest we hold off on this pull request until
> > > the regression is diagnosed.
> >
> > Thanks, Daniel. I have pushed a revert to staging.
>
> This has been diagnosed now.
>
> Old SeaBIOS would unconditionally add ACPI tables, even when QEMU
> machine type had acpi=off. libguestfs forgot to ask for ACPI in
> its libvirt XML, so was getting acpi=off as far as QEMU was
> concerned, but SeaBIOS was none the less creating ACPI tables.
>
> It was a miracle this worked because the ACPI tables were
> designed for i440fx, but somehow Linux still booted with
> them under q35.
>
> So, the SeaBIOS update has a functional change, but that
> was intentional & desirable, and the root bug was the lack
> of request for ACPI in libguestfs.
>
> So no need to revert anything
Thanks for the update!
Stefan
next prev parent reply other threads:[~2025-06-12 13:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 7:50 [PULL 0/2] Seabios 1.17.0 20250611 patches Gerd Hoffmann
2025-06-11 7:50 ` [PULL 1/2] seabios: update submodule to 1.17.0 Gerd Hoffmann
2025-06-11 7:50 ` [PULL 2/2] seabios: update binaries " Gerd Hoffmann
2025-06-11 18:01 ` [PULL 0/2] Seabios 1.17.0 20250611 patches Daniel P. Berrangé
2025-06-11 19:21 ` Stefan Hajnoczi
2025-06-12 10:16 ` Daniel P. Berrangé
2025-06-12 12:59 ` Stefan Hajnoczi [this message]
2025-06-11 18:22 ` Stefan Hajnoczi
2025-06-11 18:30 ` Thomas Huth
2025-06-11 19:09 ` Stefan Hajnoczi
2025-06-12 4:36 ` Thomas Huth
2025-06-12 13:08 ` Stefan Hajnoczi
2025-06-12 14:16 ` Gerd Hoffmann
2025-06-12 14:33 ` Stefan Hajnoczi
2025-06-12 14:40 ` Daniel P. Berrangé
2025-06-12 14:53 ` Gerd Hoffmann
2025-06-12 15:00 ` Stefan Hajnoczi
2025-06-12 15:05 ` Thomas Huth
2025-06-16 17:33 ` Stefan Hajnoczi
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=CAJSP0QXFX9QBCu3h_Od1YeqTnB7gOUKRQ8ipnyKGxtY29kGA_A@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--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).