the blk_drain_all() that is executed if the guest issues a DMA cancel
leads to a stuck main loop if the storage backend (e.g. a NFS share)
is unresponsive.
This scenario is a common case for CDROM images mounted from an
NFS share. In this case a broken NFS server can take down the
whole VM even
If the backend storage is unresponsive and we cancel a request due to
a timeout we cannot immediately destroy the AIOCB because the storage
might complete the original request laster if it is responsive again.
For this purpose allow to set the callback to NULL and ignore it in
this case.
Am 19.08.2015 um 04:53 hat Wen Congyang geschrieben:
Ping...
It might have helped to...
a) CC the qemu-block mailing list
b) CC the subsystem maintainer that should apply the patch (according to
scripts/get_maintainer.pl that's me with Berto's Acked-by)
c) include the PATCH keyword in the