From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC PATCH docs] qm: document when fs-freeze is issued for VMs
Date: Thu, 14 Aug 2025 16:45:53 +0200 [thread overview]
Message-ID: <20250814144602.423927-1-m.sandoval@proxmox.com> (raw)
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
I might be missing some condition so I am sending this to gather feedback. I
will grep the code with more gusto on monday to see if I am missing anything.
For the moment this is only about VMs and we are missing information for
containers.
qm.adoc | 17 +++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/qm.adoc b/qm.adoc
index 55633fb..a97d5cc 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -1502,11 +1502,20 @@ run as expected. Subsequent ones, until the next reboot, will only consider
parts of the filesystem that changed since then.
[[qm_qga_fsfreeze]]
-Filesystem Freeze & Thaw on Backup
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Filesystem Freeze & Thaw
+^^^^^^^^^^^^^^^^^^^^^^^^
-By default, guest filesystems are synced via the 'fs-freeze' QEMU Guest Agent
-Command when a backup is performed, to provide consistency.
+By default, if the QEMU Guest Agent is enabled in the guest's config and if the
+agent is available inside of the guest, then the virtual machine's filesystems
+are synced via the 'fs-freeze' QEMU Guest Agent Command when certain operations
+are performed. This is done to provide data consistency.
+
+A 'fs-freeze' will be issued for any of the following operations on a VM:
+
+* Performing a backups in snapshot mode
+* Performing a clone of a VM while it is running
+* Replicating a VM while it is running
+* Taking a snapshots without RAM of a running VM
On Windows guests, some applications might handle consistent backups themselves
by hooking into the Windows VSS (Volume Shadow Copy Service) layer, a
--
2.47.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-08-14 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250814144602.423927-1-m.sandoval@proxmox.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox