From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: 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
Date: Tue, 24 Feb 2026 15:54:58 +0100 [thread overview]
Message-ID: <177194454201.158886.3506702160714804119.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260105121702.20884-1-m.sandoval@proxmox.com>
On Mon, 05 Jan 2026 13:16:44 +0100, Maximiliano Sandoval wrote:
> ..and add more logging when issuing fsfreeze guest commands.
>
> The new setting takes precedence over freeze-fs-on-backup and deprecates the
> former.
>
> - At the moment taking a snapshot without RAM does not log whether there was a
> freeze/thaw, we add logs when issuing freezes/thaws.
>
> [...]
Applied, thanks! I squashed in some style fixes and for patch 6/9, I
had to make a change, since it originally caused the suspend to be
skipped. Would be great if you could re-check that and if you could
adapt the UI for the new setting too!
qemu-server:
[1/9] add a guest-fsfreeze qga setting
commit: fcc2dc56b43010b919f03c557cb8c0e2cd8bbed1
[2/9] api: clone_vm: follow guest-fsfreeze setting
commit: 08ae75f53050af225c12bd119cbc369d08e23efc
[3/9] fix #1964: follow guest-fsfreeze setting on check freeze needed
commit: 9d3597007835d50db2d3659520612eceddfb05a8
[4/9] agent: add a guest_fsthaw helper
commit: 90fde50a3ed15ab20ac6685c8918268b5e30f43e
[5/9] port users of guest-fsfreeze-thaw users to helper
commit: 0fb2256e45aff699d628fbc7dd978e65ae2703f3
[6/9] block job: log when a fsfreeze could not happen
commit: 09d8fa8031509beea77ac2da1339b51b6740194d
[7/9] block job: mirror: reword fsfreeze log entry
commit: 2bbaaed5fea7d2d8d8736a77e8cd35eedd258a27
[8/9] deprecate freeze-fs-on-backup qga setting
commit: d82c5e7e997510a12cdc6ed7ee0c00773184bd4b
[9/9] api: import: follow guest-fsfreeze setting
commit: 7546da2cf680035ba33122db770ba20c8f5c3c6f
guest-common:
[1/1] abstract config: print when {, un}freezing a fs
commit: da78acdd5a66a0b916306bfd373654ea03074b78
pve-docs:
[1/1] qm: document that import-from can issue a fsfreeze
commit: 862cd43b09245de212332bc3b9b03dae0de7ccb8
prev parent reply other threads:[~2026-02-24 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 12:16 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-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 ` Fiona Ebner [this message]
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=177194454201.158886.3506702160714804119.b4-ty@proxmox.com \
--to=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.