From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH qemu-server v3 2/2] migration: conntrack: avoid crash when dbus-vmstate object cannot be added (quickly enough)
Date: Tue, 7 Oct 2025 14:25:01 +0200 [thread overview]
Message-ID: <20251007122509.66194-3-f.ebner@proxmox.com> (raw)
In-Reply-To: <20251007122509.66194-1-f.ebner@proxmox.com>
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
This is after the configuration is already moved and thus there also
is no source instance running anymore.
Change the type of the 'pve-dbus-vmstate@' service to 'notify', so
that starting the service returns success only after the
'dbus-vmstate' object has been added to the QEMU instance.
[0]: https://forum.proxmox.com/threads/172588/
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
Dependency bump qemu-server -> pve-common needed.
No changes in v3.
src/usr/dbus-vmstate | 3 +++
src/usr/pve-dbus-vmstate@.service | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/usr/dbus-vmstate b/src/usr/dbus-vmstate
index ac6f8cfb..b2baa840 100755
--- a/src/usr/dbus-vmstate
+++ b/src/usr/dbus-vmstate
@@ -15,6 +15,7 @@ use Net::DBus::Reactor;
use PVE::QemuServer::Helpers;
use PVE::QemuServer::QMPHelpers qw(qemu_objectadd qemu_objectdel);
use PVE::SafeSyslog;
+use PVE::Systemd;
use PVE::Tools;
use base qw(Net::DBus::Object);
@@ -165,4 +166,6 @@ qemu_objectadd($vmid, 'pve-vmstate', 'dbus-vmstate',
'id-list' => "pve-vmstate-$vmid",
);
+PVE::Systemd::sd_notify(0, "READY=1\n");
+
Net::DBus::Reactor->main()->run();
diff --git a/src/usr/pve-dbus-vmstate@.service b/src/usr/pve-dbus-vmstate@.service
index 56b4e285..616f6979 100644
--- a/src/usr/pve-dbus-vmstate@.service
+++ b/src/usr/pve-dbus-vmstate@.service
@@ -6,5 +6,5 @@ PartOf=%i.scope
[Service]
Slice=qemu.slice
-Type=simple
+Type=notify
ExecStart=/usr/libexec/qemu-server/dbus-vmstate %i
--
2.47.3
_______________________________________________
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-10-07 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 12:24 [pve-devel] [PATCH-SERIES common/qemu-server v3 0/2] migration: conntrack: fix race adding dbus-vmstate object to QEMU Fiona Ebner
2025-10-07 12:25 ` [pve-devel] [PATCH common v3 1/2] systemd: add sd_notify() helper Fiona Ebner
2025-10-07 12:25 ` 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=20251007122509.66194-3-f.ebner@proxmox.com \
--to=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.