From: "Michael Köppl" <m.koeppl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH qemu-server v2 0/2] correctly set HA state then
Date: Thu, 27 Nov 2025 16:40:39 +0100 [thread overview]
Message-ID: <20251127154041.194423-1-m.koeppl@proxmox.com> (raw)
This series makes 2 changes to the restore functionality for VMs:
- Correctly set the HA state to 'started' for HA-managed VMs that are
live-restored, since live-restore already implies start-after-create
and otherwise the VM is shut down during restore.
- When restoring VMs that already are HA resources, set the status of
the existing resource instead of trying to add a new HA resource,
which would fail and keep the old state of the existing resource.
qemu-server:
Michael Köppl (2):
create_vm: assume HA state 'started' when live-restoring guests
create_vm: set HA state when restoring VM if resource already exists
src/PVE/API2/Qemu.pm | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
Summary over all repositories:
1 files changed, 11 insertions(+), 3 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-11-27 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 15:40 Michael Köppl [this message]
2025-11-27 15:40 ` [pve-devel] [PATCH qemu-server v2 1/2] create_vm: assume HA state 'started' when live-restoring guests Michael Köppl
2025-11-27 15:40 ` [pve-devel] [PATCH qemu-server v2 2/2] create_vm: set HA state when restoring VM if resource already exists Michael Köppl
2025-11-29 22:49 ` [pve-devel] applied: [PATCH qemu-server v2 0/2] correctly set HA state then 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=20251127154041.194423-1-m.koeppl@proxmox.com \
--to=m.koeppl@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