10.04.2024 10:55, Steev Klimaszewski wrote:
I wanted to try if 8.2.2, or 9.0 has a fix, but due to the time64 change, I cannot use packages from unstable or experimental at this time as Kali is based on Debian testing. I did try cloning the repository to build it myself in a kali sbuild chroot, however I got some unrelated error message about the xz file being corrupt.
You can download qemu-user-static .deb of any version and install it in your environment - it is a self-contained package (since it is linked statically) not requiring any time64 changes. Speaking of xz file being corrupt - I'd love to know more details about this one. As of the bug itself, - it would be very interesting to see which change in 8.1.4 caused this problem (hopefully I got it right and it's been introduced in 8.1.4 - actually, introduced in master and backported to 8.1.4). Please install a build environment (minimal is enough, with libglib-dev, libz-dev, meson, python3-venv - and maybe a few others which I forgot about, - you'll know after the first try). Clone the qemu git repository, build just qemu-x86_64-static binary: ../configure --target-list=x86_64-linux-user --enable-static && make qemu-x86_64 and try bisecting between v8.1.3 and v8.1.4 (or maybe try other versions if it is not in 8.1.4 - eg, check if 8.2.0 works but 8.2.3 doesn't, etc). You'll have to re-load binfmt registration after updating the binary in /usr/bin/qemu-x86_64-static - kernel keeps old binary open. Just use `cat /usr/lib/binfmt.d/qemu-x86_64.conf > /proc/sys/fs/binfmt_misc/register' or re-run systemd-binfmt.service. It would be difficult for me to try it here since I don't have the hardware. Maybe you can create a smaller testcase as well. Thanks, /mjt
