From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container/ha-manager/qemu-server 0/5] Small HA-on-create improvements
Date: Mon, 17 Nov 2025 17:11:42 +0100 [thread overview]
Message-ID: <DEB3OE6N8PVO.9RFY4L5VSIPG@proxmox.com> (raw)
In-Reply-To: <20251110143627.365434-1-d.kral@proxmox.com>
Tested this series by:
- manually adding a resource to the config and running `ha-manager
relocate ...` right after. With the patches applied, this no longer
fails
- creating a VM through `qm create <vmid> --ha-managed 1`
- running `qmrestore` with the --start flag explicitly set to 1 or 0 or
omitting it
- running `qmrestore` with the --ha-managed flag explicitly set to 1 or
0 or omitting it
- creating a CT through `pct create <vmid> <ostemplate> --ha-managed 1`
The changes made all of the above work as expected. Thanks for fixing
these! Also had a look at the code and the changes lgtm!
Consider this:
Tested-by: Michael Köppl <m.koeppl@proxmox.com>
Reviewed-by: Michael Köppl <m.koeppl@proxmox.com>
On Mon Nov 10, 2025 at 3:36 PM CET, Daniel Kral wrote:
> Some small fixes and improvements while playing around with the
> HA-on-create feature related mainly to the CLI usage. Two qemu-server
> patches only enhance the usage by allowing --ha-managed and --start
> parameters for qmrestore.
>
> pve-ha-manager.git:
>
> Daniel Kral (1):
> api: resources: fix uninitialized value in check_service_state
>
> src/PVE/API2/HA/Resources.pm | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
>
> qemu-server.git:
>
> Daniel Kral (3):
> api: create_vm: use ha-manager command to add VM as an HA resource
> qmrestore: allow starting a VM after it was restored successfully
> qmrestore: allow adding a VM as an HA resource after it was restored
>
> src/PVE/API2/Qemu.pm | 10 ++++------
> src/PVE/CLI/qmrestore.pm | 12 ++++++++++++
> 2 files changed, 16 insertions(+), 6 deletions(-)
>
>
> pve-container.git:
>
> Daniel Kral (1):
> api: create_vm: use ha-manager command to add container as an HA
> resource
>
> src/PVE/API2/LXC.pm | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
>
> Summary over all repositories:
> 4 files changed, 22 insertions(+), 10 deletions(-)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-17 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 14:36 Daniel Kral
2025-11-10 14:36 ` [pve-devel] [PATCH ha-manager 1/1] api: resources: fix uninitialized value in check_service_state Daniel Kral
2025-11-17 21:37 ` [pve-devel] applied: " Thomas Lamprecht
2025-11-10 14:36 ` [pve-devel] [PATCH qemu-server 1/3] api: create_vm: use ha-manager command to add VM as an HA resource Daniel Kral
2025-11-17 21:27 ` Thomas Lamprecht
2025-11-10 14:36 ` [pve-devel] [PATCH qemu-server 2/3] qmrestore: allow starting a VM after it was restored successfully Daniel Kral
2025-11-17 21:27 ` Thomas Lamprecht
2025-11-10 14:36 ` [pve-devel] [PATCH qemu-server 3/3] qmrestore: allow adding a VM as an HA resource after it was restored Daniel Kral
2025-11-17 21:27 ` Thomas Lamprecht
2025-11-10 14:36 ` [pve-devel] [PATCH container 1/1] api: create_vm: use ha-manager command to add container as an HA resource Daniel Kral
2025-11-17 21:27 ` [pve-devel] applied: " Thomas Lamprecht
2025-11-17 16:11 ` Michael Köppl [this message]
2025-11-17 16:24 ` [pve-devel] applied: [PATCH container/ha-manager/qemu-server 0/5] Small HA-on-create improvements 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=DEB3OE6N8PVO.9RFY4L5VSIPG@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=pve-devel-bounces@lists.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