From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH qemu-server v3 3/3] fix #7119: qm cleanup: wait for process exiting for up to 30 seconds
Date: Thu, 26 Feb 2026 14:52:02 +0100 [thread overview]
Message-ID: <20260226140752.1792378-4-d.csapak@proxmox.com> (raw)
In-Reply-To: <20260226140752.1792378-1-d.csapak@proxmox.com>
When qmeventd detects a vm exiting, it starts 'qm cleanup'.
Since the vm process exits is sometimes not instant, wait up to 30
seconds here to start the cleanup process instead of immediately
aborting if the pid still exits. This prevented executing the hookscript
on the 'post-stop' phase when either
* the cleanup mechanism is still the old one
* the guest was powered down from inside, not via the API
This can be reproduced by e.g. passing through a usb device, which
delays the qemu process exit for a few seconds (for most devices).
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
src/PVE/CLI/qm.pm | 16 ++++++++++++++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/src/PVE/CLI/qm.pm b/src/PVE/CLI/qm.pm
index 6aff5b7a..ee3ccedd 100755
--- a/src/PVE/CLI/qm.pm
+++ b/src/PVE/CLI/qm.pm
@@ -1101,7 +1101,7 @@ __PACKAGE__->register_method({
60,
sub {
my $conf = PVE::QemuConfig->load_config($vmid);
- my $pid = PVE::QemuServer::check_running($vmid);
+ my $pid = PVE::QemuServer::Helpers::vm_running_locally($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
@@ -1109,7 +1109,19 @@ __PACKAGE__->register_method({
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;
+ # wait for some time until the QEMU process exits after the QMP
+ # 'SHUTDOWN' event, since this might not be instant
+ my $timeout = 30;
+ my $starttime = time();
+ warn "QEMU process $pid for VM $vmid still running (or newly started)\n"
+ if $pid;
+
+ while ($pid && (time() - $starttime) < $timeout) {
+ sleep(1);
+ $pid = PVE::QemuServer::check_running($vmid);
+ }
+
+ die "vm still running after timeout - aborting cleanup\n" if $pid;
# Rollback already does cleanup when preparing and afterwards temporarily drops the
# lock on the configuration file to rollback the volumes. Deactivating volumes here
--
2.47.3
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 ` [PATCH qemu-server v3 2/3] qm cleanup: die early when encountering a running stop mode backup Dominik Csapak
2026-02-26 13:52 ` Dominik Csapak [this message]
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-4-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox