From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES qemu-server 0/3] fix migration status handling (for QEMU 10.0+)
Date: Mon, 28 Jul 2025 16:30:30 +0200 [thread overview]
Message-ID: <20250728143042.103045-1-f.ebner@proxmox.com> (raw)
There are some states that 'query-migrate' can return [0] which are
not properly handled by Proxmox VE yet.
In particular, as reported in the community forum [1], with QEMU 10.0,
the 'device' status can be present with migration parameters used by
Proxmox VE.
Two other states 'cancelling' and 'wait-unplug' are also explicitly
handled now.
[0]: https://qemu.readthedocs.io/en/master/interop/qemu-qmp-ref.html#enum-QMP-migration.MigrationStatus
[1]: https://forum.proxmox.com/threads/proxmox-ve-9-0-beta-released.168619/post-786535
Fiona Ebner (3):
migration: status check: order states in regex alphabetically
migration: handle 'device' migration status newly present in QEMU
10.0+
migration: handle 'cancelling' and 'wait-unplug' status
src/PVE/QemuMigrate.pm | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--
2.47.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-07-28 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 14:30 Fiona Ebner [this message]
2025-07-28 14:30 ` [pve-devel] [PATCH qemu-server 1/3] migration: status check: order states in regex alphabetically Fiona Ebner
2025-07-28 14:30 ` [pve-devel] [PATCH qemu-server 2/3] migration: handle 'device' migration status newly present in QEMU 10.0+ Fiona Ebner
2025-07-28 14:30 ` [pve-devel] [PATCH qemu-server 3/3] migration: handle 'cancelling' and 'wait-unplug' status Fiona Ebner
2025-07-29 6:05 ` [pve-devel] [PATCH-SERIES qemu-server 0/3] fix migration status handling (for QEMU 10.0+) Thomas Lamprecht
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=20250728143042.103045-1-f.ebner@proxmox.com \
--to=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