From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 42B281FF13C for ; Thu, 25 Jun 2026 13:45:21 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A4C1BEEF0; Thu, 25 Jun 2026 13:45:13 +0200 (CEST) From: Samuel Rufinatscha To: pve-devel@lists.proxmox.com Subject: [PATCH qemu-server 0/1] fix #7590: qemu-server: apply timeout to QEMU start fork Date: Thu, 25 Jun 2026 13:44:59 +0200 Message-ID: <20260625114500.159384-1-s.rufinatscha@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1782387903111 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.221 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [qemuserver.pm,proxmox.com] Message-ID-Hash: CGAHJENJ5VODQVSOU6RBMQO5GXIJDIWV X-Message-ID-Hash: CGAHJENJ5VODQVSOU6RBMQO5GXIJDIWV X-MailFrom: s.rufinatscha@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: This series makes the forked QEMU start path use the existing start timeout. If the timeout expires, it terminates processes in the VM scope and cleans up QSD before reporting the start failure. This prevents a stuck qmstart task from holding the VM config lock indefinitely or leaving a partially started QEMU process running. Tested with QEMU blocked on a FIFO (see the reproducer at [0]). qmstart timed out and released the lock, leaving no active scope or QEMU process. Normal VM startup still works. [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7590 Samuel Rufinatscha (1): fix #7590: qemu-server: apply timeout to QEMU start fork src/PVE/QemuServer.pm | 28 +++++++++++++++++++++++++++- 1 file changed, 27 insertions(+), 1 deletion(-) -- 2.47.3