From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Erik Fastermann <e.fastermann@proxmox.com>
Subject: partially-applied: [PATCH qemu v2 0/9] savevm-async: fix stuck paused vm after snapshot
Date: Tue, 8 Sep 2026 16:21:52 +0200 [thread overview]
Message-ID: <178887727784.249651.2956102114551397886.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260907094744.131193-1-e.fastermann@proxmox.com>
On Mon, 07 Sep 2026 11:47:34 +0200, Erik Fastermann wrote:
> Snapshotting a paused VM left it in finish-migrate, where it stayed
> until the VM was restarted. Fix this by storing the run state instead
> and put it back, similar to migration_iteration_finish().
>
> While working on that, I noticed some memory leaks and other issues,
> which I found by using sanitizer tools like ASAN and reading the code
> and docs.
>
> [...]
Applied the first five patches, thanks!
[1/9] d/patches: normalize header of pbs-restore no-cache patch
commit: 7498b1bd7b71da1465631267620400b541d1de15
[2/9] pbs-restore: keep callback data on the stack
commit: 10fd013483270154354657766e6645ca3e63af24
[3/9] migration/qemu-file: allocate buffer with g_malloc
commit: 45d5a170a7c8628b1c743417b7e3d2a65a67033f
[4/9] migration/pbs-state: check allocation of incoming state buffer
commit: b6f2adbcea48c6b13613d638fc45643d4181471e
[5/9] savevm-async: drop QIOChannel reference
commit: 513917f9a745c641c6a783d35dd340beb469b785
prev parent reply other threads:[~2026-09-08 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 9:47 [PATCH qemu v2 0/9] savevm-async: fix stuck paused vm after snapshot Erik Fastermann
2026-09-07 9:47 ` [PATCH qemu v2 1/9] d/patches: normalize header of pbs-restore no-cache patch Erik Fastermann
2026-09-07 9:47 ` [PATCH qemu v2 2/9] pbs-restore: keep callback data on the stack Erik Fastermann
2026-09-07 9:47 ` [PATCH qemu v2 3/9] migration/qemu-file: allocate buffer with g_malloc Erik Fastermann
2026-09-07 9:47 ` [PATCH qemu v2 4/9] migration/pbs-state: check allocation of incoming state buffer Erik Fastermann
2026-09-07 9:47 ` [PATCH qemu v2 5/9] savevm-async: drop QIOChannel reference Erik Fastermann
2026-09-08 14:22 ` Fiona Ebner
2026-09-07 9:47 ` [PATCH qemu v2 6/9] savevm-async: free migration vmdesc Erik Fastermann
2026-09-08 14:22 ` Fiona Ebner
2026-09-07 9:47 ` [PATCH qemu v2 7/9] savevm-async: release resources on start failure path Erik Fastermann
2026-09-07 9:47 ` [PATCH qemu v2 8/9] savevm-async: include reason when file open fails Erik Fastermann
2026-09-07 9:47 ` [PATCH qemu v2 9/9] savevm-async: restore run state from before snapshot Erik Fastermann
2026-09-08 14:22 ` Fiona Ebner
2026-09-08 14:21 ` Fiona Ebner [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=178887727784.249651.2956102114551397886.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=e.fastermann@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.