From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40])
	by lore.proxmox.com (Postfix) with ESMTPS id 47B9F1FF0B3
	for <inbox@lore.proxmox.com>; Wed, 28 Oct 2026 17:16:35 +0100 (CET)
Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1])
	by gate001.proxmox.com (Proxmox) with ESMTP id 9BADC214FB;
	Wed, 28 Oct 2026 17:16:23 +0100 (CET)
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Samuel Rufinatscha <s.rufinatscha@proxmox.com>
Subject: applied: [PATCH qemu-server v2 0/1] fix #7590: apply timeout to QEMU
 start fork
Date: Wed, 28 Oct 2026 17:16:07 +0100
Message-ID: <179320416732.1677009.10058935523990981744.b4-ty@b4>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20260803172152.331208-1-s.rufinatscha@proxmox.com>
References: <20260803172152.331208-1-s.rufinatscha@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: 1793204177760
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.482 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_MED        -2.3 Sender listed at https://www.dnswl.org/,
 medium 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: SBEDLY5ZSWNWWNATICLHEZZZKD726IWM
X-Message-ID-Hash: SBEDLY5ZSWNWWNATICLHEZZZKD726IWM
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 <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.proxmox.com>

On Mon, 03 Aug 2026 19:21:51 +0200, Samuel Rufinatscha wrote:
> The qmstart task forks a child process that enters the VM scope, starts
> the helper processes and launches QEMU. qmstart then waits for the
> child to report success or failure. While regular starts already apply
> $start_timeout to the QEMU command, the wait for the forked child has
> no timeout. Statefile starts do not use the QEMU command timeout
> either, leaving both waits unbounded.
> 
> [...]

Applied, thanks!

[1/1] fix #7590: qemu-server: apply timeout to QEMU start fork
      https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=14faa1dc340ab467deabf3185caec4c56dba38ff