[PATCH] vdpa: Avoid reset when stop device

From: Michael Qiu Currently, when VM poweroff, it will trigger vdpa device(such as mlx bluefield2 VF) reset twice, this leads to below issue: vhost VQ 2 ring restore failed: -22: Invalid argument (22) This because in vhost_dev_stop(), qemu tries to stop the device, then stop the queue: vhost_vi

[PATCH v2] vdpa: reset the backend device in stage of stop last vhost device

From: Michael Qiu Currently, when VM poweroff, it will trigger vdpa device(such as mlx bluefield2 VF) reset many times(with 1 datapath queue pair and one control queue, triggered 3 times), this leads to below issue: vhost VQ 2 ring restore failed: -22: Invalid argument (22) This because in vhos

[PATCH v3] vdpa: reset the backend device in the end of vhost_net_stop()

From: Michael Qiu Currently, when VM poweroff, it will trigger vdpa device(such as mlx bluefield2 VF) reset many times(with 1 datapath queue pair and one control queue, triggered 3 times), this leads to below issue: vhost VQ 2 ring restore failed: -22: Invalid argument (22) This because in vhos

[PATCH] Fix crash with IOthread when block commit after snapshot

From: Michael Qiu Currently, if guest has workloads, IO thread will acquire aio_context lock before do io_submit, it leads to segmentfault when do block commit after snapshot. Just like below: [Switching to thread 2 (Thread 0x7f046c312700 (LWP 108791))] #0 0x5573f57930db in bdrv_mirror_top_p

[PATCH] Fix crash with IOthread when block commit after snapshot

From: Michael Qiu Currently, if guest has workloads, IO thread will acquire aio_context lock before do io_submit, it leads to segmentfault when do block commit after snapshot. Just like below: [Switching to thread 2 (Thread 0x7f046c312700 (LWP 108791))] #0 0x5573f57930db in bdrv_mirror_top_p

[PATCH v2] Fix crash with IOthread when block commit after snapshot

From: Michael Qiu v2: modify the coredump backtrace within commit log with the newest qemu with master branch Currently, if guest has workloads, IO thread will acquire aio_context lock before do io_submit, it leads to segmentfault when do block commit after snapshot. Just like below: Progra

[PATCH v3] Fix crash with IOthread when block commit after snapshot

From: Michael Qiu v3: reformat the commit log, remove duplicate content v2: modify the coredump backtrace within commit log with the newest qemu with master branch Currently, if guest has workloads, IO thread will acquire aio_context lock before do io_submit, it leads to segmentfault when d

[PATCH v4] blockjob: Fix crash with IOthread when block commit after snapshot

From: Michael Qiu v4: rebase to latest code v3: reformat the commit log, remove duplicate content v2: modify the coredump backtrace within commit log with the newest qemu with master branch Currently, if guest has workloads, IO thread will acquire aio_context lock before do io_submit, it l

[PATCH] blockjob: Fix crash with IOthread when block commit after snapshot

From: Michael Qiu v5: reformat the commit log with backtrace of main thread Add a boolean variable to make main thread could re-acquire aio_context on success path. v4: rebase to latest code v3: reformat the commit log, remove duplicate content Currently, if guest has workloads, IO thr

[Qemu-devel] [PATCH] Fix coredump when using virtio-vga

From: Michael Qiu When using command -device virtio-vga,virgl=on the default max_outputs is 0, this will lead coredump, (con=0x0, hw_ops=0x564452e0 , opaque=0x5754ec60) at ui/console.c:1872 (vpci_dev=0x5754ec60, errp=0x7fffdbb8) at qemu/hw/display/virtio-vga.c:1