Hi Christian, sorry I missed your updates on this one. I've only just
come back to the issue yesterday and apparently I've hit another issue:
bug #1908331 "Regression: qemu-user-static binaries are dynamically
linked"
That side-tracked me whilst trying to do the git-bisect and I've still
not solved that bug - spent the best part of 8 hours on it. I was going
to ping you on IRC later today.
I've pulled in your backport build and extracted just qemu-
aarch64-static. It's currently running and is unpacking so I *think*
this has solved the current issue, BUT, it looks to be affected by the
bug mentioned above as well:
$ file ../qemu-aarch64_v5.0-backport
../qemu-aarch64_v5.0-backport: ELF 64-bit LSB shared object, x86-64, version 1
(GNU/Linux), dynamically linked,
BuildID[sha1]=31ee6e0f3235e1d9a6da328cfa6a25c7b4c92487, for GNU/Linux 3.2.0,
stripped
$ ldd ../qemu-aarch64_v5.0-backport
statically linked
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906479
Title:
qemu:handle_cpu_signal received signal outside vCPU context
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906479/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
