Because of a systemd issue [0], when a service that's 'partOf' a scope fails, the scope itself might end up being left-over, even after all processes in the scope exit. In particular, this can happen for the '$vmid.scope' when the 'pve-dbus-vmstate@$vmid.service' fails.
As reported in the community forum [1], 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. [0]: https://github.com/systemd/systemd/issues/39141 [1]: https://forum.proxmox.com/threads/172588/ qemu-server: Fiona Ebner (3): dbus vmstate: add missing includes migration: conntrack: work around systemd issue where scope for VM might become blocked migration: conntrack: avoid crash when dbus-vmstate object cannot be added (quickly enough) src/PVE/QemuServer.pm | 6 ++++++ src/PVE/QemuServer/DBusVMState.pm | 15 +++++++++++++++ 2 files changed, 21 insertions(+) Summary over all repositories: 2 files changed, 21 insertions(+), 0 deletions(-) -- Generated by git-murpp 0.5.0 _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
