public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Jakob Klocker" <j.klocker@proxmox.com>
To: "Michael Köppl" <m.koeppl@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu-server 1/1] fix #8030: snapshot: avoid orphaned vmstate volume on failure
Date: Tue, 22 Sep 2026 10:14:03 +0200	[thread overview]
Message-ID: <DLLP10M6PF5M.2GJML8JH4HB6W@proxmox.com> (raw)
In-Reply-To: <20260914140547.615346-1-m.koeppl@proxmox.com>

Confirmed that an orphaned volume is left behind when the QMP
socket is occupied, causing the snapshot to fail because
`query-machines` times out. After applying the patch, no orphaned
volume remains, which fixes the reported bug.

Not adding additional cleanup, but moving the disk allocation below
the setup functions that can fail is IMO the cleanest solution here.

Consider this:
Reviewed-by: Jakob Klocker <j.klocker@proxmox.com>
Tested-by: Jakob Klocker <j.klocker@proxmox.com>
On Mon Sep 14, 2026 at 4:05 PM CEST, Michael Köppl wrote:
> The state volume was allocated before the running instance was queried
> for its machine type, CPU argument and network MTUs. Those queries can
> fail (e.g. the 'query-machines' QMP command, which can run into a
> timeout while QEMU's is busy [0]).
>
> The helper is called from __snapshot_prepare() before write_config(), so
> the config never records the snapshot, snapshot_create() dies before it
> gets to its cleanup path. Such a failure leaves behind the just
> allocated volume.
>
> Query the running instance first, which makes the allocation the last
> step of the function that can fail.
>
> [0] https://bugzilla.proxmox.com/show_bug.cgi?id=8030
>
> Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
> [SNIP]




  reply	other threads:[~2026-09-22  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 14:05 [PATCH qemu-server 1/1] fix #8030: snapshot: avoid orphaned vmstate volume on failure Michael Köppl
2026-09-22  8:14 ` Jakob Klocker [this message]
2026-09-22  8:44 ` Elias Huhsovitz
2026-09-22 13:26 ` applied: " Fiona Ebner

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=DLLP10M6PF5M.2GJML8JH4HB6W@proxmox.com \
    --to=j.klocker@proxmox.com \
    --cc=m.koeppl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal