Started to recheck where things have broken: In fresh containers do: #0 - prep tools $ apt install ubuntu-dev-tools qemu-user-static qemu-kvm #1 - check sid guest $ pbuilder-dist sid arm64 create #2 - check bionic guest $ pbuilder-dist bionic arm64 create
1. Ubuntu releases T - fails #1 (not in scope of this bug) X - fails #2 - __spawnix: Assertion `ec >= 0' failed Z - fails #2 - __spawnix: Assertion `ec >= 0' failed A - fails #2 - different error msg but also at bash package (might be the same) B - fails #2 - different error msg but also at bash package (might be the same) We can eliminate host glibc from the equation by using Ubuntu cloud archive in Xenial. X - Newton (~Xenial/Yakkety) - fails #2 - __spawnix: Assertion `ec >= 0' failed X - Ocata (=Zesty) - fails #2 - __spawnix: Assertion `ec >= 0' failed X - Pike (=Artful/Bionic) - fails #2 - __spawnix: Assertion `ec >= 0' failed It is worth to mention that also all related fixes e.g. [1] are in glibc. That and the fact that it doesn't seem to be a regression in the virt stack as first assumed indicates that it could more likely be the glibc in the guest that triggers all that. So lets inverse the test and take all the virt stacks we have and run it against artful, zesty, ... backwards. $ pbuilder-dist zesty arm64 create X/X-Newton/X-Ocata/X-Pike/Z/A/B - all work $ pbuilder-dist artful arm64 create X/X-Newton/X-Ocata/X-Pike/Z/A/B - all fail Ok, given the tests and references we have I nack this as a qemu issue and instead declare it a glibc issue in >=Artful. But the change that e.g. [1] carries is too much over my head to decide anything. IMHO even very minor changes there are much more real problems than [2] - yet for Bionic which isn't released one could change it. [1]: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=4b4d4056bb154603f36c6f8845757c1012758158;hp=8d3bd947483f50b57aee7c35c07dc1927d6e8a27 [2]: https://xkcd.com/1172/ ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Invalid ** Also affects: glibc (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Artful) Importance: Undecided Status: New ** No longer affects: qemu (Ubuntu Artful) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737312 Title: Qemu crashes with signal 6 on arm64 chroot creation on amd64 (installing bash) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1737312/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
