From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH-SERIES qemu-server v2 0/7] fix #7383: agent: fsfreeze: skip freeze if already frozen
Date: Thu, 23 Apr 2026 14:35:11 +0200 [thread overview]
Message-ID: <20260423124004.115303-1-f.ebner@proxmox.com> (raw)
Changes in v2:
* Drop already applied patches.
* Rebase on master, making use of the new should_fs_freeze() function.
* Add patch to switch to v5.36 and use subroutine signatures.
* Add patch renaming guest_fs{freeze,thaw} to guest_fs_{freeze,thaw}.
* Drop patch for changing signature of get_qga_key().
* Rename guest_fsfreeze_applicable() to guest_fs_freeze_applicable().
* Simplify log function (usage) in guest_fsfreeze_applicable().
* Drop $is_backup argument from guest_fs_freeze_applicable() now that
there is no backup-specific option anymore (is an alias for the
general one).
* Pass guest agent config for move disk caller of clone_disk() for
completenetss.
The first patch migrates the agent module to use v5.36 and subroutine
signatures.
The second patch renames guest_fs{freeze,thaw} to
guest_fs_{freeze,thaw} for consistency with should_fs_freeze().
The next four patches lead up to harmonizing the checks for guest
filesystem freeze which previously were duplicated to three different
places and improve encapsulation of the agent module.
The last patch closes bug #7383 and checks if the filesystem is
already frozen before attempting freeze to avoid a confusing error
message.
qemu-server:
Fiona Ebner (7):
agent: migrate to v5.36 and use subroutine signatures
agent: rename guest_fs{freeze,thaw} to guest_fs_{freeze,thaw}
agent: parse: change signature to take property string rather than
full VM config
agent: should fs freeze: change signature to take property string
rather than full VM config
clone disk/block jobs: change signatures to take guest agent property
string
agent: fs freeze: harmonize checks for guest fs freeze
fix #7383: agent: fsfreeze: skip freeze if already frozen
src/PVE/API2/Qemu.pm | 10 +--
src/PVE/QMPClient.pm | 2 +-
src/PVE/QemuConfig.pm | 18 +++--
src/PVE/QemuServer.pm | 8 +--
src/PVE/QemuServer/Agent.pm | 121 +++++++++++++++++++++------------
src/PVE/QemuServer/BlockJob.pm | 19 ++----
src/PVE/VZDump/QemuServer.pm | 24 +++----
7 files changed, 109 insertions(+), 93 deletions(-)
Summary over all repositories:
7 files changed, 109 insertions(+), 93 deletions(-)
--
Generated by git-murpp 0.5.0
next reply other threads:[~2026-04-23 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 12:35 Fiona Ebner [this message]
2026-04-23 12:35 ` [PATCH qemu-server v2 1/7] agent: migrate to v5.36 and use subroutine signatures Fiona Ebner
2026-04-23 12:35 ` [PATCH qemu-server v2 2/7] agent: rename guest_fs{freeze,thaw} to guest_fs_{freeze,thaw} Fiona Ebner
2026-04-23 12:35 ` [PATCH qemu-server v2 3/7] agent: parse: change signature to take property string rather than full VM config Fiona Ebner
2026-04-23 12:35 ` [PATCH qemu-server v2 4/7] agent: should fs freeze: " Fiona Ebner
2026-04-23 12:35 ` [PATCH qemu-server v2 5/7] clone disk/block jobs: change signatures to take guest agent property string Fiona Ebner
2026-04-23 12:35 ` [PATCH qemu-server v2 6/7] agent: fs freeze: harmonize checks for guest fs freeze Fiona Ebner
2026-04-23 12:35 ` [PATCH qemu-server v2 7/7] fix #7383: agent: fsfreeze: skip freeze if already frozen 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=20260423124004.115303-1-f.ebner@proxmox.com \
--to=f.ebner@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