Hi TJ,
that reminds me of some bugs for arm* chroots with static that we fixed 
recently.
Hmm no, that was bug 1890881 which isn't completely the same - but it also was 
not backportable to 20.04 anyway :-/

I've checked my inbox and found plenty of upstream references to this in
https://bugs.launchpad.net/qemu/+bug/1785203
https://bugs.launchpad.net/qemu/+bug/1594394
https://bugs.launchpad.net/qemu/+bug/1815911
https://bugs.launchpad.net/qemu/+bug/1793539

According to these the bug should be fixed by:
https://git.qemu.org/?p=qemu.git;a=commit;h=0acd4ab849827bbc20402e01c9da088207c0d236
https://git.qemu.org/?p=qemu.git;a=commit;h=2a03d3e6ae1b1ca86199a0c36a35e8ac847905f6
But those are in >3.1 / >4.1 -so they would be in Focals 4.2 already.

Since there was so much movement in this area I tried the newer qemu from [1]. 
I've run your test steps with that qemu 5.0 and it works fine for me.
  $ sudo chroot debian-sid-aarch64 aptitude full-upgrade
  ...
  Current status: 0 (-151) upgradable.

So qemu 5.0 in groovy and later should be ok, I wonder what fix in particular 
that might be.
Maybe after all still something related to bug 1890881 (or the patches 
submitted related to it since - as mentioned - there were many linux-user 
changes)?
We'll need to identify those to be able to decide if we can SRU this, but one 
step at a time.

Could you give [1] a try for your case/system/setup as well please -
just to make sure it isn't just my system that works?

[1]: https://launchpad.net/~canonical-server/+archive/ubuntu/server-
backports

** Also affects: qemu (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Changed in: qemu (Ubuntu)
       Status: New => Fix Released

-- 
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to