From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server v5 8/9] deprecate freeze-fs-on-backup qga setting
Date: Tue, 17 Mar 2026 12:32:36 +0100 [thread overview]
Message-ID: <723da55e-ff27-4ea6-8163-53e525eb1de7@proxmox.com> (raw)
In-Reply-To: <753dcbdb-6170-4076-b8b6-a1fb3d8907b1@proxmox.com>
Am 17.03.26 um 10:40 schrieb Fiona Ebner:
>> why not just make this an alias for the new (superset) property?
> If we think most people set the property because the VM had issues with
> freezing, which are not actually limited to the backup case, then having
> it be an alias can be sensible. I do think this is the case, but it
> might still be surprising to some people. We could also wait until PVE
> 10 to have it become an alias or...
I mean the option is also made for that assumption, isn't it? Because
otherwise we would need to make it a "flag list" (sorta like the
features for LXC config) to actually provide full control on when to
freeze and when not.
As a boolean flag with just the name changed it IMO intended to be a
superset of the backup one, as introducing then a specific flag for clone,
snapshot, replication, ...? would be much better solved by a flag list,
that then would also avoid users wondering for when this is actually done,
as that can be seen by the selected options. But not a must to do now,
mostly also because that needs some dedicated handling as the qemu-server
was already released...
>> And you certainly *cannot* remove this in PVE 10, doing so will break
>> restoring previous backups!
> ...just translate the option to the more general one in
> restore_update_config_line() and/or parse_config(), then we could drop
> it from the schema.
That needs to be remembered though, with the current comment and how
this was applied I rather doubt that doing so was on the radar... And,
while that can be done, it's not like it's without implication, as
backup and restoring that again on an older PVE would make it fail
even if one did not change the VM at all. Not something we (can) provide
hard guarantees for, but certainly not something I want to actively break,
especially without good reason.
next prev parent reply other threads:[~2026-03-17 11:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 12:16 [pve-devel] [PATCH docs/guest-common/qemu-server v5 00/11] fix #1964: add setting to always disable freezing a guest's fs Maximiliano Sandoval
2026-01-05 12:16 ` [pve-devel] [PATCH qemu-server v5 1/9] add a guest-fsfreeze qga setting Maximiliano Sandoval
2026-01-05 12:16 ` [pve-devel] [PATCH qemu-server v5 2/9] api: clone_vm: follow guest-fsfreeze setting Maximiliano Sandoval
2026-01-05 12:16 ` [pve-devel] [PATCH qemu-server v5 3/9] fix #1964: follow guest-fsfreeze setting on check freeze needed Maximiliano Sandoval
2026-01-05 12:16 ` [pve-devel] [PATCH qemu-server v5 4/9] agent: add a guest_fsthaw helper Maximiliano Sandoval
2026-01-05 12:16 ` [pve-devel] [PATCH qemu-server v5 5/9] port users of guest-fsfreeze-thaw users to helper Maximiliano Sandoval
2026-01-05 12:16 ` [pve-devel] [PATCH qemu-server v5 6/9] block job: log when a fsfreeze could not happen Maximiliano Sandoval
2026-01-05 12:16 ` [pve-devel] [PATCH qemu-server v5 7/9] block job: mirror: reword fsfreeze log entry Maximiliano Sandoval
2026-01-05 12:16 ` [pve-devel] [PATCH qemu-server v5 8/9] deprecate freeze-fs-on-backup qga setting Maximiliano Sandoval
2026-03-16 21:50 ` Thomas Lamprecht
2026-03-17 8:21 ` Maximiliano Sandoval
2026-03-17 9:40 ` Fiona Ebner
2026-03-17 11:32 ` Thomas Lamprecht [this message]
2026-03-17 11:54 ` Fiona Ebner
2026-01-05 12:16 ` [pve-devel] [PATCH qemu-server v5 9/9] api: import: follow guest-fsfreeze setting Maximiliano Sandoval
2026-01-05 12:16 ` [pve-devel] [PATCH guest-common v5 1/1] abstract config: print when {, un}freezing a fs Maximiliano Sandoval
2026-01-05 12:16 ` [pve-devel] [PATCH docs v5 1/1] qm: document that import-from can issue a fsfreeze Maximiliano Sandoval
2026-02-24 14:54 ` applied-series: [pve-devel] [PATCH docs/guest-common/qemu-server v5 00/11] fix #1964: add setting to always disable freezing a guest's fs Fiona Ebner
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=723da55e-ff27-4ea6-8163-53e525eb1de7@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=m.sandoval@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.