From: Thomas Huth <1838658@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1838658] Re: qemu 4.0.0 broken by glib update
Date: Thu, 10 Dec 2020 08:48:46 -0000 [thread overview]
Message-ID: <160759012612.31246.2584347515254966347.malone@soybean.canonical.com> (raw)
In-Reply-To: 156467368424.6955.5535032657029646608.malonedeb@soybean.canonical.com
Released with QEMU v5.2.0.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1838658
Title:
qemu 4.0.0 broken by glib update
Status in QEMU:
Fix Released
Bug description:
In brief, an install CD will successfully boot with qemu 4.0.0 built with glib 2.58.3, but freeze during boot with qemu 4.0.0 built with glib 2.60.0. I tracked it down to glib's GHashTable improvements. qemu is happy with a glib built from
```
git checkout -f 2.60.4
git revert --no-edit 86c6f7e2b..3bed8a13b
git revert --no-edit 75f8ec1df9b48b0c3a13a9125f2c7d7c5adf5159
git revert --no-edit 603fb5958..d3074a748
git revert --no-edit 0b45ddc55..0600dd322
```
When the GHashTable improvements were committed, there was already a preemptive note about any breakage being due to using private implementation details, hence mentioning it here rather than with glib.
For the full saga, see: http://gnats.netbsd.org/54310
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1838658/+subscriptions
prev parent reply other threads:[~2020-12-10 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 15:34 [Qemu-devel] [Bug 1838658] [NEW] qemu 4.0.0 broken by glib update Patrick Welche
2019-08-02 5:11 ` Markus Armbruster
2019-08-02 8:25 ` [Qemu-devel] [Bug 1838658] " Daniel Berrange
2019-08-02 8:42 ` Daniel Berrange
2019-08-02 15:56 ` Andreas Gustafsson
2019-08-02 16:17 ` Andreas Gustafsson
2019-08-02 16:52 ` Daniel Berrange
2019-08-02 19:31 ` Andreas Gustafsson
2020-11-21 22:58 ` Peter Maydell
2020-12-10 8:48 ` 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=160759012612.31246.2584347515254966347.malone@soybean.canonical.com \
--to=1838658@bugs.launchpad.net \
--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).