From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: applied-rest: [PATCH-SERIES qemu/qemu-server v2 0/5] fix #6424: avoid timeout issue for QMP 'quit' for bulk suspend
Date: Mon, 13 Jul 2026 16:42:44 +0200 [thread overview]
Message-ID: <178395373441.294242.15060549433080187518.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260629135438.172004-1-f.ebner@proxmox.com>
On Mon, 29 Jun 2026 15:54:16 +0200, Fiona Ebner wrote:
> Changes in v2:
> * rebase on current master
> * use qemu-stable v11.0.2
>
> I was able to reproduce the issue for a VM without IO thread busy
> with IO on a heavily rate-limited storage.
>
> [...]
Applied, thanks!
[3/5] fix #6424: increase timeout for QMP 'quit' to 60s to avoid issue with bulk suspend
commit: a0960ff1aeed0e38dedd91334f513240c388f2e9
[4/5] run state: use v5.36 and signatures in module
commit: 51483f06045fce2f77d22a477795e274ad3653c0
[5/5] suspend: skip VM start after successfully saving state
commit: 1ea4e92b2046989701314c32f3ccf1b4493f29c0
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
prev parent reply other threads:[~2026-07-13 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 13:54 [PATCH-SERIES qemu/qemu-server v2 0/5] fix #6424: avoid timeout issue for QMP 'quit' for bulk suspend Fiona Ebner
2026-06-29 13:54 ` [PATCH qemu v2 1/5] async snapshot: allow skipping VM start after successful completion Fiona Ebner
2026-06-29 13:54 ` [PATCH qemu v2 2/5] update submodule and patches to QEMU 11.0.2 Fiona Ebner
2026-06-29 13:54 ` [PATCH qemu-server v2 3/5] fix #6424: increase timeout for QMP 'quit' to 60s to avoid issue with bulk suspend Fiona Ebner
2026-06-29 13:54 ` [PATCH qemu-server v2 4/5] run state: use v5.36 and signatures in module Fiona Ebner
2026-06-29 13:54 ` [PATCH qemu-server v2 5/5] suspend: skip VM start after successfully saving state Fiona Ebner
2026-07-13 14:42 ` Fabian Grünbichler [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=178395373441.294242.15060549433080187518.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox