From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH qemu-server v3 2/3] qm cleanup: die early when encountering a running stop mode backup
Date: Thu, 26 Feb 2026 14:52:01 +0100 [thread overview]
Message-ID: <20260226140752.1792378-3-d.csapak@proxmox.com> (raw)
In-Reply-To: <20260226140752.1792378-1-d.csapak@proxmox.com>
this is an expected situation, so abort here early with a better message
than 'vm still running'
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
src/PVE/CLI/qm.pm | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/src/PVE/CLI/qm.pm b/src/PVE/CLI/qm.pm
index b7bc4d9f..6aff5b7a 100755
--- a/src/PVE/CLI/qm.pm
+++ b/src/PVE/CLI/qm.pm
@@ -1102,6 +1102,13 @@ __PACKAGE__->register_method({
sub {
my $conf = PVE::QemuConfig->load_config($vmid);
my $pid = PVE::QemuServer::check_running($vmid);
+
+ # With a stop mode backup, we might run here into a running vm with a backup
+ # lock, but this already did the cleanup and is an expected state, so abort
+ # here with a good message
+ die "skipping cleanup - 'backup' lock is present and vm is running again\n"
+ if $pid && $clean && $conf->{lock} && $conf->{lock} eq 'backup';
+
die "vm still running\n" if $pid;
# Rollback already does cleanup when preparing and afterwards temporarily drops the
--
2.47.3
next prev parent reply other threads:[~2026-02-26 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 13:51 [PATCH qemu-server v3 0/3] improve guest cleanup handling Dominik Csapak
2026-02-26 13:52 ` [PATCH qemu-server v3 1/3] cleanup: refactor to make cleanup flow consistent Dominik Csapak
2026-02-26 13:52 ` Dominik Csapak [this message]
2026-02-26 13:52 ` [PATCH qemu-server v3 3/3] fix #7119: qm cleanup: wait for process exiting for up to 30 seconds Dominik Csapak
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=20260226140752.1792378-3-d.csapak@proxmox.com \
--to=d.csapak@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.