the commit that was mentioned in [2],
b5b6e8c8d3b4cbeb447a0f10c7d5de3caa573299, forces blk_mq for virtio_scsi,
so it cannot be disabled for new kernels.
Any hint on how to avoid this hang while still having virtio-scsi disks
and blk_mq enabled please?
Thanks.
--
Oleksandr Natalenko (post-factum)
[1]
http
ndeed, I can confirm that these commits fix the issue.
Thanks a lot.
--
Oleksandr Natalenko (post-factum)
> +QLIST_INSERT_HEAD_RCU(&ctx->deleted_aio_handlers, node,
> node_deleted);
> +}
> +
> QSLIST_REMOVE_HEAD_RCU(&ctx->submit_list, node_submitted);
> -QLIST_REMOVE(node, node);
> -g_free(node);
> }
c.c
> index 3165a28f2f..1319eee3bc 100644
> --- a/util/async.c
> +++ b/util/async.c
> @@ -362,6 +362,7 @@ static GSourceFuncs aio_source_funcs = {
>
> GSource *aio_get_g_source(AioContext *ctx)
> {
> +aio_context_use_g_source(ctx);
> g_source_ref(&ctx->source);
> return &ctx->source;
> }
Tested-by: Oleksandr Natalenko
(run Windows 10 VM with storage accessible via io_uring on qemu v5.0.0
with these 2 patches)
Thank you.
--
Best regards,
Oleksandr Natalenko (post-factum)
Principal Software Maintenance Engineer
