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.eb...@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
