Looking closer we've just noticed the bullseye's ldconfig claims to be dynamically linked but buster's is statically linked.
This reminds of bug #1908331 we solved earlier this year in qemu itself due to the build flag -static-pie
$ file bullseye-arm64/sbin/ldconfig bullseye-arm64/sbin/ldconfig: ELF 64-bit LSB shared object, ARM aarch64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=6cca288a8f9e39114be7ce6d9761f252990f5214, for GNU/Linux 3.7.0, stripped $ file buster-arm64/sbin/ldconfig buster-arm64/sbin/ldconfig: ELF 64-bit LSB executable, ARM aarch64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.7.0, BuildID[sha1]=078feba3f88616e37d2a77a1997d9de2343df80b, stripped
Looking closer we've just noticed the bullseye's ldconfig claims to be dynamically linked but buster's is statically linked.
This reminds of bug #1908331 we solved earlier this year in qemu itself due to the build flag -static-pie
$ file bullseye- arm64/sbin/ ldconfig arm64/sbin/ ldconfig: ELF 64-bit LSB shared object, ARM aarch64, version 1 (GNU/Linux), dynamically linked, BuildID[ sha1]=6cca288a8 f9e39114be7ce6d 9761f252990f521 4, for GNU/Linux 3.7.0, stripped arm64/sbin/ ldconfig arm64/sbin/ ldconfig: ELF 64-bit LSB executable, ARM aarch64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.7.0, BuildID[ sha1]=078feba3f 88616e37d2a77a1 997d9de2343df80 b, stripped
bullseye-
$ file buster-
buster-