From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 7EAC81FF17C for ; Tue, 30 Dec 2025 16:32:28 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DE503EA17; Tue, 30 Dec 2025 16:33:34 +0100 (CET) From: Maximiliano Sandoval To: Fiona Ebner In-Reply-To: <4a946522-661c-4cd5-adbf-b122b0b4eb0e@proxmox.com> (Fiona Ebner's message of "Thu, 4 Dec 2025 15:03:04 +0100") References: <20251014122718.374205-1-m.sandoval@proxmox.com> <20251014122718.374205-5-m.sandoval@proxmox.com> <4a946522-661c-4cd5-adbf-b122b0b4eb0e@proxmox.com> User-Agent: mu4e 1.12.9; emacs 30.1 Date: Tue, 30 Dec 2025 16:33:00 +0100 Message-ID: MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1767108753229 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.089 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.001 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.001 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.001 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 Subject: Re: [pve-devel] [PATCH qemu-server v3 4/7] log when issuing a guest-fsfreeze command X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Cc: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Fiona Ebner writes: > Am 14.10.25 um 2:27 PM schrieb Maximiliano Sandoval: >> These messages appear during replication or snapshots. >> >> The messages will now appear on all call sites of __snapshot_freeze(). >> >> Signed-off-by: Maximiliano Sandoval >> --- >> src/PVE/QemuConfig.pm | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/src/PVE/QemuConfig.pm b/src/PVE/QemuConfig.pm >> index 412c76ae..32a95dd6 100644 >> --- a/src/PVE/QemuConfig.pm >> +++ b/src/PVE/QemuConfig.pm >> @@ -310,9 +310,11 @@ sub __snapshot_freeze { >> my ($class, $vmid, $unfreeze) = @_; >> >> if ($unfreeze) { >> + print "issuing guest agent 'guest-fsfreeze-thaw' command\n"; >> eval { mon_cmd($vmid, "guest-fsfreeze-thaw"); }; >> warn "guest-fsfreeze-thaw problems - $@" if $@; >> } else { >> + print "issuing guest agent 'guest-fsfreeze-freeze' command\n"; >> eval { PVE::QemuServer::Agent::guest_fsfreeze($vmid); }; >> warn $@ if $@; >> } > > Maybe there should be a PVE::QemuServer::Agent::guest_fsthaw() helper > and the messages should go into the Agent::guest_fs{freeze,thaw}() > helpers directly rather than on all call sites. Avoids duplication and > improves consistency. The problem is that half of the users would prefer to log with a logging function, adding a `$logfunc` parameter to these two helpers can be OK, but it also requires changes in LXC.pm. -- Maximiliano _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel