From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 qemu-server] resume: bump timeout for query-status
Date: Mon, 29 Jul 2024 19:16:02 +0200 [thread overview]
Message-ID: <6d7fcdf0-f3d3-42b5-b73c-d4134d731c00@proxmox.com> (raw)
In-Reply-To: <20240725123226.51239-1-f.ebner@proxmox.com>
Am 25/07/2024 um 14:32 schrieb Fiona Ebner:
> As reported in the community forum [0], after migration, the VM might
> not immediately be able to respond to QMP commands, which means the VM
> could fail to resume and stay in paused state on the target.
>
> The reason is that activating the block drives in QEMU can take a bit
> of time. For example, it might be necessary to invalidate the caches
> (where for raw devices a flush might be needed) and the request
> alignment and size of the block device needs to be queried.
>
> In [0], an external Ceph cluster with krbd is used, and the initial
> read to the block device after migration, for probing the request
> alignment, takes a bit over 10 seconds[1]. Use 60 seconds as the new
> timeout to be on the safe side for the future.
>
> All callers are inside workers or via the 'qm' CLI command, so bumping
> beyond 30 seconds is fine.
>
> [0]: https://forum.proxmox.com/threads/149610/
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>
> Changes in v2:
> * improve commit message with new findings from the forum thread
>
> PVE/QemuServer.pm | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
>
applied, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-07-29 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 12:32 [pve-devel] " Fiona Ebner
2024-07-29 17:16 ` Thomas Lamprecht [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=6d7fcdf0-f3d3-42b5-b73c-d4134d731c00@proxmox.com \
--to=t.lamprecht@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