From: Ubuntu SRU Bot <2123828@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 2123828] Autopkgtest regression report (qemu/1:10.1.0+ds-5ubuntu2.1)
Date: Thu, 23 Oct 2025 06:36:09 -0000 [thread overview]
Message-ID: <20251023063609.D6E69FC1E7@ubuntu-archive-toolbox.internal> (raw)
In-Reply-To: 175793222278.1250191.6568998309826575823.malonedeb@juju-98d295-prod-launchpad-2
All autopkgtests for the newly accepted qemu (1:10.1.0+ds-5ubuntu2.1) for questing have finished running.
The following regressions have been reported in tests triggered by the package:
livecd-rootfs/25.10.24 (s390x)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/questing/update_excuses.html#qemu
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/2123828
Title:
[SRU] RISC-V: incorrect emulation of load and store on big-endian
systems
Status in QEMU:
Fix Released
Status in glibc package in Ubuntu:
Invalid
Status in qemu package in Ubuntu:
Fix Committed
Status in gcc-15 source package in Noble:
Invalid
Status in glibc source package in Noble:
Invalid
Status in qemu source package in Noble:
In Progress
Status in gcc-15 source package in Plucky:
Invalid
Status in glibc source package in Plucky:
Invalid
Status in qemu source package in Plucky:
In Progress
Status in gcc-15 source package in Questing:
Invalid
Status in glibc source package in Questing:
Invalid
Status in qemu source package in Questing:
Fix Committed
Status in glibc source package in Resolute:
Invalid
Status in qemu source package in Resolute:
Fix Committed
Bug description:
[ Impact ]
On s390x architecture, qemu cannot emulate riscv64 well because of an
endianess error. Original bug report :
QEMU's DEP-8 test fails on s390x, due to warning output on stderr
about "unsupported version 256 of Verdef record", which is blocking
migration of glibc 2.42-0ubuntu3.
DEP-8 logs:
"""
323s === Checking if /usr/bin/qemu-riscv64 can run executables:
323s glob with sh: /usr/bin/qemu-riscv64 /bin/busybox ash -c "/usr/bin/qemu-riscv64 /bin/busybox ls -dCFl debian/*[t]*":
323s /bin/busybox: /lib/ld-linux-riscv64-lp64d.so.1: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/riscv64-linux-gnu/libresolv.so.2: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/ld-linux-riscv64-lp64d.so.1: unsupported version 256 of Verdef record
323s
323s Reading package lists.../bin/busybox: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/ld-linux-riscv64-lp64d.so.1: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/ld-linux-riscv64-lp64d.so.1: unsupported version 256 of Verdef record
323s /bin/busybox: /lib/ld-linux-riscv64-lp64d.so.1: unsupported version 256 of Verdef record
323s Expected output not found
[...]
328s autopkgtest [22:14:52]: @@@@@@@@@@@@@@@@@@@@ summary
328s test-qemu-img.sh PASS (superficial)
328s test-qemu-system.sh PASS (superficial)
328s test-qemu-user.sh FAIL stderr: /bin/busybox: /lib/ld-linux-riscv64-lp64d.so.1: unsupported version 256 of Verdef record
"""
Patched by flagging the faulty instructions with the endianness swap
marker.
[ Test Plan ]
Minimal reproducer: (after booting up an s390x vm)
```
ubuntu@slyon-lp-2123828-slyon-glibc-qemu-riscv64:~$ sudo apt update && sudo apt install qemu-user
ubuntu@slyon-lp-2123828-slyon-glibc-qemu-riscv64:~$ dpkg -l | grep libc6
ii libc6:s390x 2.42-0ubuntu3
ubuntu@slyon-lp-2123828-slyon-glibc-qemu-riscv64:~$ dpkg -l | grep qemu-user
ii qemu-user 1:10.1.0+ds-5ubuntu1
ubuntu@slyon-lp-2123828-slyon-glibc-qemu-riscv64:~$ dpkg --print-architecture
s390x
ubuntu@slyon-lp-2123828-slyon-glibc-qemu-riscv64:~$ sudo dpkg --add-architecture riscv64
ubuntu@slyon-lp-2123828-slyon-glibc-qemu-riscv64:~$ sudo apt update
ubuntu@slyon-lp-2123828-slyon-glibc-qemu-riscv64:~$ sudo apt install hello:riscv64
ubuntu@slyon-lp-2123828-slyon-glibc-qemu-riscv64:~$ /usr/bin/qemu-riscv64 /usr/bin/hello
/usr/bin/hello: /lib/ld-linux-riscv64-lp64d.so.1: unsupported version 256 of Verdef record
/usr/bin/hello: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
/usr/bin/hello: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
/usr/bin/hello: /lib/riscv64-linux-gnu/libc.so.6: unsupported version 256 of Verdef record
/usr/bin/hello: /lib/ld-linux-riscv64-lp64d.so.1: unsupported version 256 of Verdef record
/usr/bin/hello: /lib/ld-linux-riscv64-lp64d.so.1: unsupported version 256 of Verdef record
/usr/bin/hello: /lib/ld-linux-riscv64-lp64d.so.1: unsupported version 256 of Verdef record
```
The same thing with the patch shows "Hello, world !".
[ Where problems could occur ]
This change is really small (3 lines), and only affects riscv64
emulation from QEMU. If the fix was entirely wrong, riscv64 emulation
of compressed instruction could be affected. It can be easily tested.
The patch was accepted upstream, so such tests are conducted upstream
as well, which reduces the amount of possible problems and work to do
to fix those.
[ Other Info ]
Patch applied upstream: https://gitlab.com/qemu-project/qemu/-/commit/b25133d38fe693589cf695b85968caa0724bfafd
Patch available on ppa: https://launchpad.net/~vhaudiquet/+archive/ubuntu/qemu-fix-lp2123828/+packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/2123828/+subscriptions
next prev parent reply other threads:[~2025-10-23 6:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <175793222278.1250191.6568998309826575823.malonedeb@juju-98d295-prod-launchpad-2>
2025-09-26 7:37 ` [Bug 2123828] Re: unsupported version 256 of Verdef record when running qemu-riscv64 on s390x Heinrich Schuchardt
2025-09-26 7:58 ` Simon Chopin
2025-09-26 7:47 ` Heinrich Schuchardt
2025-09-26 9:44 ` Bug Watch Updater
2025-09-26 10:31 ` [Bug 2123828] Re: RISC-V: incorrect emulation of load and store on big-endian systems Heinrich Schuchardt
2025-09-29 11:03 ` Valentin Haudiquet
2025-09-29 12:27 ` Launchpad Bug Tracker
2025-10-03 4:31 ` Heinrich Schuchardt
2025-10-03 7:19 ` Valentin Haudiquet
2025-10-03 9:59 ` Valentin Haudiquet
2025-10-03 10:10 ` Valentin Haudiquet
2025-10-04 15:09 ` [Bug 2123828] Re: [SRU] " Bug Watch Updater
2025-10-06 7:45 ` Valentin Haudiquet
2025-10-06 11:50 ` Launchpad Bug Tracker
2025-10-06 12:50 ` Launchpad Bug Tracker
2025-10-06 13:22 ` Launchpad Bug Tracker
2025-10-08 7:18 ` Christian Ehrhardt
2025-10-08 8:32 ` Christian Ehrhardt
2025-10-09 13:24 ` Hector CAO
2025-10-15 7:20 ` Lukas Märdian
2025-10-22 8:34 ` Lukas Märdian
2025-10-22 18:45 ` Nick Rosbrook
2025-10-22 18:46 ` [Bug 2123828] Please test proposed package Nick Rosbrook
2025-10-23 6:36 ` Ubuntu SRU Bot [this message]
2025-10-23 7:28 ` [Bug 2123828] Re: [SRU] RISC-V: incorrect emulation of load and store on big-endian systems Lukas Märdian
2025-10-26 16:38 ` Launchpad Bug Tracker
2025-10-29 9:12 ` Lukas Märdian
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=20251023063609.D6E69FC1E7@ubuntu-archive-toolbox.internal \
--to=2123828@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).