Thanks for the feedback.

It looks like this happens because of:

     * There cannot be two concurrent aio_poll calls for the same AioContext (or
     * an aio_poll concurrent with a GSource prepare/check/dispatch callback).
     * We rely on this below to avoid slow locked accesses to ctx->notify_me.

added by the last update:

qemu (1:2.11+dfsg-1ubuntu7.27) bionic; urgency=medium                           
  * d/p/ubuntu/lp-1805256*: Fixes for QEMU on aarch64 ARM hosts
    - aio: rename aio_context_in_iothread() to in_aio_context_home_thread()
    - aio: Do aio_notify_accept only during blocking aio_poll
    - aio-posix: Assert that aio_poll() is always called in home thread
    - async: use explicit memory barriers (LP: #1805256)
    - aio-wait: delegate polling of main AioContext if BQL not held
    - aio-posix: Don't count ctx->notifier as progress when polling
 -- Rafael David Tinoco <>  Tue, 26 May 2020 17:39:21 

Is there a way you can test Eoan or Focal's version ?

Thank you for reporting this bug.

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  QEMU crash using virtio-scsi with iothread

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to