public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server v3 4/7] log when issuing a guest-fsfreeze command
Date: Tue, 30 Dec 2025 16:33:00 +0100	[thread overview]
Message-ID: <s8oo6ngkms3.fsf@proxmox.com> (raw)
In-Reply-To: <4a946522-661c-4cd5-adbf-b122b0b4eb0e@proxmox.com> (Fiona Ebner's message of "Thu, 4 Dec 2025 15:03:04 +0100")

Fiona Ebner <f.ebner@proxmox.com> 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 <m.sandoval@proxmox.com>
>> ---
>>  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


  reply	other threads:[~2025-12-30 15:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 12:27 [pve-devel] [PATCH container/guest-common/qemu-server v3 0/9] fix #1964: add setting to always disable freezing a guest Maximiliano Sandoval
2025-10-14 12:27 ` [pve-devel] [PATCH qemu-server v3 1/7] add a guest-fsfreeze qga setting Maximiliano Sandoval
2025-12-04 14:02   ` Fiona Ebner
2025-10-14 12:27 ` [pve-devel] [PATCH qemu-server v3 2/7] block job: mirror: follow guest-fsfreeze setting Maximiliano Sandoval
2025-12-04 14:02   ` Fiona Ebner
2025-10-14 12:27 ` [pve-devel] [PATCH qemu-server v3 3/7] fix #1964: follow guest-fsfreeze setting on check freeze needed Maximiliano Sandoval
2025-10-14 12:27 ` [pve-devel] [PATCH qemu-server v3 4/7] log when issuing a guest-fsfreeze command Maximiliano Sandoval
2025-12-04 14:03   ` Fiona Ebner
2025-12-30 15:33     ` Maximiliano Sandoval [this message]
2026-01-02 10:10       ` Fiona Ebner
2025-10-14 12:27 ` [pve-devel] [PATCH qemu-server v3 5/7] block job: mirror: reword fsfreeze log entry Maximiliano Sandoval
2025-10-14 12:27 ` [pve-devel] [PATCH qemu-server v3 6/7] block job: log if fs-freeze is skipped due to config Maximiliano Sandoval
2025-10-14 12:27 ` [pve-devel] [PATCH qemu-server v3 7/7] deprecate freeze-fs-on-backup qga setting Maximiliano Sandoval
2025-10-14 12:27 ` [pve-devel] [PATCH container v3 1/1] log when freezing/thawing filesystem Maximiliano Sandoval
2025-12-04 14:03   ` Fiona Ebner
2025-10-14 12:27 ` [pve-devel] [PATCH guest-common v3 1/1] replication: remove logging when freezing/thawing Maximiliano Sandoval
2025-12-04 14:03   ` Fiona Ebner
2026-01-02 14:37 ` [pve-devel] superseded: [PATCH container/guest-common/qemu-server v3 0/9] fix #1964: add setting to always disable freezing a guest Maximiliano Sandoval

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=s8oo6ngkms3.fsf@proxmox.com \
    --to=m.sandoval@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal