From: "Elias Huhsovitz" <e.huhsovitz@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:44:04 +0200 [thread overview]
Message-ID: <DLLPNZU7BRVK.OW6R2M3JUUEX@proxmox.com> (raw)
In-Reply-To: <20260914140547.615346-1-m.koeppl@proxmox.com>
Sensible change! The state information should be allocated as late as
possible on disk.
Tested using the same methodology as the bug reporter. The state-file
was not orphaned and after releasing the QMP socket, operations and
snapshots continued working as normal.
Therefore:
Reviewed-by: Elias Huhsovitz <e.huhsovitz@proxmox.com>
Tested-by: Elias Huhsovitz <e.huhsovitz@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>
> ---
> Tested this pretty much as described in the Bugzilla entry, but using a
> Perl script to connect to the QMP socket instead of socat.
>
> src/PVE/QemuConfig.pm | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/src/PVE/QemuConfig.pm b/src/PVE/QemuConfig.pm
> index 26f0fda2..2ef6c075 100644
> --- a/src/PVE/QemuConfig.pm
> +++ b/src/PVE/QemuConfig.pm
> @@ -238,8 +238,6 @@ sub __snapshot_save_vmstate {
> my $name = "vm-$vmid-state-$snapname";
> $name .= ".raw" if $scfg->{path}; # add filename extension for file base storage
>
> - my $statefile =
> - PVE::Storage::vdisk_alloc($storecfg, $target, $vmid, 'raw', $name, $size * 1024);
> my $runningmachine = PVE::QemuServer::Machine::get_current_qemu_machine($vmid);
>
> # get current QEMU -cpu argument to ensure consistency of custom CPU models
> @@ -249,6 +247,11 @@ sub __snapshot_save_vmstate {
>
> my $nets_host_mtu = PVE::QemuServer::Network::get_nets_host_mtu($vmid, $conf);
>
> + # allocate only after querying the running instance, nothing below can fail, so a failed
> + # query cannot leave an orphaned state volume behind
> + my $statefile =
> + PVE::Storage::vdisk_alloc($storecfg, $target, $vmid, 'raw', $name, $size * 1024);
> +
> if (!$suspend) {
> $conf = $conf->{snapshots}->{$snapname};
> }
next prev parent reply other threads:[~2026-09-22 8:44 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
2026-09-22 8:44 ` Elias Huhsovitz [this message]
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=DLLPNZU7BRVK.OW6R2M3JUUEX@proxmox.com \
--to=e.huhsovitz@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