From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: applied: [PATCH qemu] fix #8343, #8361: avoid QMP timeouts and VM stalls in backups of RBD disks
Date: Fri, 20 Nov 2026 15:26:29 +0100 [thread overview]
Message-ID: <179518478542.209609.6419724984138342796.b4-ty@proxmox.com> (raw)
In-Reply-To: <20261120113834.4069058-1-t.lamprecht@proxmox.com>
On Fri, 20 Nov 2026 12:38:01 +0100, Thomas Lamprecht wrote:
> For an RBD image with fast-diff, a backup queries the block status of
> each chunk, and each query waits until the requests in flight on the
> image have completed. For a disk without an iothread, QEMU waited for
> that in its main loop. Since pve-qemu-kvm 11.1.3-2, backups to a
> Proxmox Backup Server process chunks in parallel, which keeps more
> reads in flight and so makes these waits longer. The guest could stall
> meanwhile, and a backup failed when one of its QMP commands timed out.
>
> [...]
Applied, thanks! I slightly worried about qemu_rbd_co_block_status()
now yielding could break some assumption, but I couldn't find anything
and qcow2_co_block_status() can already yield too, so there is a
precedent. Still, it might be nice to propose this change upstream
too for additional feedback and diverging less.
[1/1] fix #8343, #8361: avoid QMP timeouts and VM stalls in backups of RBD disks
commit: cdca0ab83cd4dd8b36cb1f528f12ab4bafe94854
prev parent reply other threads:[~2026-11-20 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 11:38 [PATCH qemu] fix #8343, #8361: avoid QMP timeouts and VM stalls in backups of RBD disks Thomas Lamprecht
2026-11-20 14:26 ` Fiona Ebner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179518478542.209609.6419724984138342796.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.