From: Samuel Rufinatscha <s.rufinatscha@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: superseded: [PATCH qemu-server 0/1] fix #7590: qemu-server: apply timeout to QEMU start fork
Date: Mon, 3 Aug 2026 19:26:44 +0200 [thread overview]
Message-ID: <58eceab3-7a36-4e2b-a639-6e76e558e34b@proxmox.com> (raw)
In-Reply-To: <20260625114500.159384-1-s.rufinatscha@proxmox.com>
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(-)
>
prev parent reply other threads:[~2026-08-03 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 11:44 [PATCH qemu-server 0/1] fix #7590: qemu-server: apply timeout to QEMU start fork Samuel Rufinatscha
2026-06-25 11:45 ` [PATCH qemu-server 1/1] " Samuel Rufinatscha
2026-07-13 14:37 ` Fabian Grünbichler
2026-07-29 15:45 ` Samuel Rufinatscha
2026-08-03 17:26 ` Samuel Rufinatscha [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=58eceab3-7a36-4e2b-a639-6e76e558e34b@proxmox.com \
--to=s.rufinatscha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.