From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id A0E091FF165 for ; Thu, 14 Aug 2025 16:44:57 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BA05D16597; Thu, 14 Aug 2025 16:46:35 +0200 (CEST) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Date: Thu, 14 Aug 2025 16:45:53 +0200 Message-ID: <20250814144602.423927-1-m.sandoval@proxmox.com> X-Mailer: git-send-email 2.47.2 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1755182729224 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.102 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [RFC PATCH docs] qm: document when fs-freeze is issued for VMs X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Signed-off-by: Maximiliano Sandoval --- 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