From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH-SERIES qemu-server stable-bookworm 0/3] VM-state property handling improvements
Date: Mon, 6 Oct 2025 15:16:24 +0200 [thread overview]
Message-ID: <aa4cf1f8-bfec-4228-b908-342585f07c56@proxmox.com> (raw)
In-Reply-To: <20250918093842.16059-1-f.ebner@proxmox.com>
Am 18.09.25 um 11:38 schrieb Fiona Ebner:
> Backports of the already applied series here:
> https://lore.proxmox.com/pve-devel/20250917163038.488710-1-f.ebner@proxmox.com/T/
>
> There is no running-nets-host-mtu snapshot option yet in Proxmox VE 8,
> so it's only about bug #6805.
>
> Fiona Ebner (3):
> partially fix #6805: api: clone: properly remove all snapshot-related
> info
> partially fix #6805: api: modify vm config: privilege checks for
> VM-state-related properties
> vm start: remove left-over VM-state-related properties
>
> src/PVE/API2/Qemu.pm | 6 +++++-
> src/PVE/QemuServer.pm | 16 ++++++++++++++++
> 2 files changed, 21 insertions(+), 1 deletion(-)
>
For all three cherry-pick patches:
Acked-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
_______________________________________________
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-10-06 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 9:38 Fiona Ebner
2025-09-18 9:38 ` [pve-devel] [PATCH qemu-server 1/3] partially fix #6805: api: clone: properly remove all snapshot-related info Fiona Ebner
2025-09-18 9:38 ` [pve-devel] [PATCH qemu-server 2/3] partially fix #6805: api: modify vm config: privilege checks for VM-state-related properties Fiona Ebner
2025-09-18 9:38 ` [pve-devel] [PATCH qemu-server 3/3] vm start: remove left-over " Fiona Ebner
2025-10-06 13:16 ` 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=aa4cf1f8-bfec-4228-b908-342585f07c56@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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