From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id EC4251FF0F0 for ; Mon, 03 Aug 2026 19:26:48 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id B02B6214BC; Mon, 03 Aug 2026 19:26:48 +0200 (CEST) Message-ID: <58eceab3-7a36-4e2b-a639-6e76e558e34b@proxmox.com> Date: Mon, 3 Aug 2026 19:26:44 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: superseded: [PATCH qemu-server 0/1] fix #7590: qemu-server: apply timeout to QEMU start fork To: pve-devel@lists.proxmox.com References: <20260625114500.159384-1-s.rufinatscha@proxmox.com> Content-Language: en-US From: Samuel Rufinatscha In-Reply-To: <20260625114500.159384-1-s.rufinatscha@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.133 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust 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: AXGRUOO6NFT4ZSIJUF6GYNO2EG77RINU X-Message-ID-Hash: AXGRUOO6NFT4ZSIJUF6GYNO2EG77RINU 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: https://lore.proxmox.com/pve-devel/20260803172152.331208-1-s.rufinatscha@proxmox.com/T/#t On 6/25/26 1:45 PM, Samuel Rufinatscha wrote: > 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(-) >