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 699C91FF136 for ; Mon, 18 May 2026 12:47:07 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 704C3BBB1; Mon, 18 May 2026 12:47:05 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Dominik Csapak Subject: applied: [PATCH qemu-server v5 0/3] improve guest cleanup handling Date: Mon, 18 May 2026 12:46:23 +0200 Message-ID: <177909704328.3037978.11473518831845296016.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260515122437.3153051-1-d.csapak@proxmox.com> References: <20260515122437.3153051-1-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779101179339 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.004 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: KXVOOQA5KFQZHKWRC7BHVNSNK3WVJIOJ X-Message-ID-Hash: KXVOOQA5KFQZHKWRC7BHVNSNK3WVJIOJ X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Fri, 15 May 2026 14:23:03 +0200, Dominik Csapak wrote: > First we make the cleanup handling more consistent (1/3) > then we check explicitely for the backup lock to improve the error > message for stop backup mode (2/3) > and then we fix #7119 by waiting up to 30s for a possibly still running > guest to stop (e.g. this can occur when using usb passthrouh) (3/3) > > changes from v4: > * only warn after 10 seconds exactly once, to indicate this is not a > normal situation > * drop the 'waiting for xx seconds' from warning message > > [...] Applied, thanks! [1/3] cleanup: refactor to make cleanup flow consistent commit: 7d48d8ba6fff6cda24c00adc8aedc9c6b3b46e52 [2/3] qm cleanup: die early when encountering a running stop mode backup commit: dd0fe2dfd6abe7a0af8faacfec755337a4d138be [3/3] fix #7119: qm cleanup: wait for process exiting for up to 30 seconds commit: adebb9715ce9cea0adca36f6684726b3a3a32a47 A few small fix-ups: - Bumped the preinst threshold from 9.1.12 to 9.1.13, the version this actually landed in. - Added an optional skip_hookscript param to vm_stop_cleanup and pass it true from QemuMigrate's source-side call - moving exec_hookscript into vm_stop_cleanup would otherwise newly fire the hook on every migration (the previous callsite was short-circuited there). Might be good to cross check though. - Made the preinst marker write best-effort (touch ... || echo "..." >&2) so a /run hiccup downgrades to a warning instead of aborting the upgrade. - Renamed the marker to /run/qemu-server/force-legacy-cleanup; clearer intent than 'use_old_cleanup'. - Shortened the commit message body to roughly half.