From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server v4 2/2] migration: conntrack: avoid crash when dbus-vmstate object cannot be added (quickly enough)
Date: Wed, 12 Nov 2025 15:23:34 +0100 [thread overview]
Message-ID: <176295741278.1175891.9667600445355367746.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251029100646.27658-3-f.ebner@proxmox.com>
On Wed, 29 Oct 2025 11:06:25 +0100, Fiona Ebner wrote:
> As reported in the community forum [0], it might happen that the
> dbus-vmstate object is not added (quickly enough) to the target QEMU
> instance, before the migration state is loaded. This would result in
> a crash of the target instance:
>
> > kvm: Unknown savevm section or instance 'dbus-vmstate/dbus-vmstate'
> > 0. Make sure that your current VM setup matches your saved VM setup,
> > including any hotplugged devices
> > kvm: load of migration failed: Invalid argument
>
> [...]
Applied, thanks!
[2/2] migration: conntrack: avoid crash when dbus-vmstate object cannot be added (quickly enough)
commit: fcb2c64a296007af137a9550de0f112df9cfcfef
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-11-12 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 10:06 [pve-devel] [PATCH-SERIES common/qemu-server v4 0/2] migration: conntrack: fix race adding dbus-vmstate object to QEMU Fiona Ebner
2025-10-29 10:06 ` [pve-devel] [PATCH common v4 1/2] systemd: add notify() helper Fiona Ebner
2025-11-12 14:12 ` [pve-devel] applied: " Thomas Lamprecht
2025-10-29 10:06 ` [pve-devel] [PATCH qemu-server v4 2/2] migration: conntrack: avoid crash when dbus-vmstate object cannot be added (quickly enough) Fiona Ebner
2025-11-12 14:23 ` Thomas Lamprecht [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=176295741278.1175891.9667600445355367746.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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.