From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, "Michael Köppl" <m.koeppl@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server v2 0/2] correctly set HA state then
Date: Sat, 29 Nov 2025 23:49:02 +0100 [thread overview]
Message-ID: <176445653897.1120579.16709206848041225884.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251127154041.194423-1-m.koeppl@proxmox.com>
On Thu, 27 Nov 2025 16:40:39 +0100, Michael Köppl wrote:
> 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.
>
> [...]
Applied, thanks!
[1/2] create_vm: assume HA state 'started' when live-restoring guests
commit: f9298ec1e1b14f4fc78b520d4c9e15c23c5f4516
[2/2] create_vm: set HA state when restoring VM if resource already exists
commit: 8546fe50039cf976062bd013107f5e09e172c95d
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-11-29 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 15:40 [pve-devel] " Michael Köppl
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 ` 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=176445653897.1120579.16709206848041225884.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.