Re: Are user static builds really dynamically linked ?

On 16/12/2020 11:39, Paolo Bonzini wrote: > On 16/12/20 12:07, Peter Maydell wrote: >> Something has definitely changed here. What you had with 4.2.1 >> is what you should be getting. The obvious suspect is that >> something weird happened in the meson conversion... Ubuntu/Debian maintainer

Are user static builds really dynamically linked ?

user --static builds are apparently resulting in dynamically linked executables (to the glibc library, not other shared objects ) Concise summary: $ file ../qemu-aarch64_v* ../qemu-aarch64_v4.2.1: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked,

qemu:handle_cpu_signal received signal outside vCPU context

We're seeing this error on Ubuntu 20.04 amd64 host and aarch64 qemu-aarch64-static chroot when executing 'aptitude': qemu:handle_cpu_signal received signal outside vCPU context qemu:handle_cpu_signal received signal outside vCPU context Research led us to an identical issue report against