public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu-server v2 4/4] qga: rename guest-fsfreeze to freeze-fs
Date: Thu, 26 Mar 2026 10:08:33 +0100	[thread overview]
Message-ID: <s8ocy0rot4e.fsf@toolbox> (raw)
In-Reply-To: <20260325213415.3861690-5-t.lamprecht@proxmox.com> (Thomas Lamprecht's message of "Wed, 25 Mar 2026 22:28:05 +0100")

Thomas Lamprecht <t.lamprecht@proxmox.com> writes:

> These settings are already in the (QEMU guest) agent property, and we
> do not use the guest- prefix for any of the existing properties
> (fstrim or freeze-fs-on-backup), and moving freeze-fs-on-backup to a
> generic variant is less confusing if one just drops the "-on-backup"
> part, i.e. no point in inventing a new name schema just for the sake
> of it.
>
> We already rolled this the guest-fsfreeze name to pve-test, so lets
> add an alias, but as we do not provide API stability guarantees for
> test packages this is really just for convenience for anybody that
> tested this, I'm more than fine with dropping such a (never stable)
> released key again on a major release with the respective upgrade
> check in our pveXtoY tool.
>
> Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

For the sake of documenting, the rationale behind the "guest-fsfreeze"
name was using the guest agent command names, namely
"guest-fsfreeze-freeze" and "guest-fsfreeze-thaw", as a base.

For a long time I struggled to find the actual name of these commands
and their documentation since they are named ever-so-slightly
differently each time they appear on the docs or UI: "fsfreeze",
"freeze", "fs-freeze", etc.

If anything, I personally found the old name to be a source of confusion.

> ---
>  src/PVE/QemuServer/Agent.pm         | 9 +++++++--
>  src/test/cfg2cmd/qga-fs-freeze.conf | 2 +-
>  2 files changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/src/PVE/QemuServer/Agent.pm b/src/PVE/QemuServer/Agent.pm
> index b0abd7c0..23dbb3ff 100644
> --- a/src/PVE/QemuServer/Agent.pm
> +++ b/src/PVE/QemuServer/Agent.pm
> @@ -38,9 +38,14 @@ our $agent_fmt = {
>      'freeze-fs-on-backup' => {
>          type => 'boolean',
>          optional => 1,
> -        alias => 'guest-fsfreeze', # keep for old backup restore compatibility
> +        alias => 'freeze-fs', # keep for old backup restore compatibility
>      },
>      'guest-fsfreeze' => {
> +        type => 'boolean',
> +        optional => 1,
> +        alias => 'freeze-fs', # TODO: was only on test repo, drop with PVE 10.
> +    },
> +    'freeze-fs' => {
>          description => "Freeze guest filesystems through QGA for consistent disk state on"
>              . " operations such as snapshots, backups, replications and clones.",
>          verbose_description =>
> @@ -211,7 +216,7 @@ sub should_fs_freeze {
>  
>      my $agent = parse_guest_agent($conf);
>      return 0 if !$agent->{enabled};
> -    return $agent->{'guest-fsfreeze'} // 1;
> +    return $agent->{'freeze-fs'} // 1;
>  }
>  
>  =head3 guest_fsfreeze
> diff --git a/src/test/cfg2cmd/qga-fs-freeze.conf b/src/test/cfg2cmd/qga-fs-freeze.conf
> index c32e143e..809b7d43 100644
> --- a/src/test/cfg2cmd/qga-fs-freeze.conf
> +++ b/src/test/cfg2cmd/qga-fs-freeze.conf
> @@ -1,2 +1,2 @@
>  # TEST: Ensure agent sub-properties do not affect the QEMU command line.
> -agent: 1,guest-fsfreeze=1
> +agent: 1,freeze-fs=1

-- 
Maximiliano




  reply	other threads:[~2026-03-26  9:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 21:28 [PATCH qemu-server v2 0/4] rework fs-freeze agent property Thomas Lamprecht
2026-03-25 21:28 ` [PATCH qemu-server v2 1/4] agent: add should_fs_freeze helper Thomas Lamprecht
2026-03-26 12:55   ` Fiona Ebner
2026-03-27  1:12     ` Thomas Lamprecht
2026-03-25 21:28 ` [PATCH qemu-server v2 2/4] agent: treat freeze-fs-on-backup as alias for guest-fsfreeze Thomas Lamprecht
2026-03-26 12:55   ` Fiona Ebner
2026-03-26 23:05     ` Thomas Lamprecht
2026-03-27  8:53       ` Fiona Ebner
2026-03-25 21:28 ` [PATCH qemu-server v2 3/4] tests: cfg2cmd: add agent guest-fsfreeze config tests Thomas Lamprecht
2026-03-26 12:55   ` Fiona Ebner
2026-03-25 21:28 ` [PATCH qemu-server v2 4/4] qga: rename guest-fsfreeze to freeze-fs Thomas Lamprecht
2026-03-26  9:08   ` Maximiliano Sandoval [this message]
2026-03-26 21:46     ` Thomas Lamprecht
2026-03-26 12:55   ` Fiona Ebner
2026-03-26 23:16 ` applied: [PATCH qemu-server v2 0/4] rework fs-freeze agent property 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=s8ocy0rot4e.fsf@toolbox \
    --to=m.sandoval@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@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