From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id E43F11FF13C for ; Thu, 19 Mar 2026 16:26:37 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E197636BF; Thu, 19 Mar 2026 16:26:50 +0100 (CET) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Subject: [PATCH qemu-server] agent: remove feature removal todo note Date: Thu, 19 Mar 2026 16:26:38 +0100 Message-ID: <20260319152643.481736-1-m.sandoval@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1773933961235 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.940 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.408 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.819 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.903 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: BOOLGY7AHS5SDLUHTU6EASIWITP7ABRX X-Message-ID-Hash: BOOLGY7AHS5SDLUHTU6EASIWITP7ABRX X-MailFrom: m.sandoval@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Thomas Lamprecht X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Removing this option would make restoring backups which have this feature enable fail. Suggested-by: Thomas Lamprecht Signed-off-by: Maximiliano Sandoval --- Notes: This addresses part of the feedback at [1]. This is still missing implementing an alias from the review. I will look into it on the coming days. [1] https://lore.proxmox.com/all/9320e19a-94a9-452a-aedd-eea21a0572bf@proxmox.com/T/#u src/PVE/QemuServer/Agent.pm | 1 - 1 file changed, 1 deletion(-) diff --git a/src/PVE/QemuServer/Agent.pm b/src/PVE/QemuServer/Agent.pm index fb3e1835..7bf38e1c 100644 --- a/src/PVE/QemuServer/Agent.pm +++ b/src/PVE/QemuServer/Agent.pm @@ -35,7 +35,6 @@ our $agent_fmt = { optional => 1, default => 0, }, - # TODO Remove for Proxmox VE 10 'freeze-fs-on-backup' => { description => "Deprecated: Use 'guest-fsfreeze' instead.\n\n" . "Freeze/thaw guest filesystems on backup for consistency.", -- 2.47.3