From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container/guest-common/qemu-server 0/3] log when freezing or thawing the guest's fs
Date: Fri, 29 Aug 2025 13:43:33 +0200 [thread overview]
Message-ID: <20250829114337.345358-1-m.sandoval@proxmox.com> (raw)
At the moment taking a snapshot without RAM does not log whether there was a freeze/thaw.
This does not add an extra log line when making a Backup in snapshot mode.
qemu-server:
Maximiliano Sandoval (1):
log when issues a guest-fsfreeze command
src/PVE/QemuConfig.pm | 2 ++
1 file changed, 2 insertions(+)
pve-container:
Maximiliano Sandoval (1):
log when freezing/thawing filesystem
src/PVE/LXC/Config.pm | 2 ++
1 file changed, 2 insertions(+)
qemu-server:
Maximiliano Sandoval (1):
replication: remove logging when freezing/thawing
src/PVE/Replication.pm | 2 --
1 file changed, 2 deletions(-)
Summary over all repositories:
3 files changed, 4 insertions(+), 2 deletions(-)
--
Generated by murpp 0.9.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-08-29 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 11:43 Maximiliano Sandoval [this message]
2025-08-29 11:43 ` [pve-devel] [PATCH qemu-server 1/1] log when issues a guest-fsfreeze command Maximiliano Sandoval
2025-08-29 11:45 ` Maximiliano Sandoval
2025-08-29 11:43 ` [pve-devel] [PATCH container 1/1] log when freezing/thawing filesystem Maximiliano Sandoval
2025-08-29 11:43 ` [pve-devel] [PATCH guest-common 1/1] replication: remove logging when freezing/thawing Maximiliano Sandoval
2025-09-01 13:03 ` [pve-devel] [PATCH container/guest-common/qemu-server 0/3] log when freezing or thawing the guest's fs Shannon Sterz
2025-09-02 12:46 ` [pve-devel] superseded: " Maximiliano Sandoval
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=20250829114337.345358-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