>>> "Ulrich Windl" <[email protected]> schrieb am 12.07.2021 um 08:35 in Nachricht <[email protected]>: > Hi! > > We had some problem in the cluster that prevented live migration of VMs. As
> a consequence the cluster migrated the VMs using stop/start. As a side-note: It was found that Update libvirt-daemon-6.0.0-13.13.1.x86_64 of SLES15 SP2 seems to overwrite the configuration file /etc/sysconfig/libvirtd, causing the LIBVIRTD_ARGS="--listen" to be dropped. Running libvirtd without the "--listen" parameter seemed to cause the migration failures. Kind of proof: # ll /etc/sysconfig/libvirtd -rw-r--r-- 1 root root 642 Jun 8 08:20 /etc/sysconfig/libvirtd # rpm -qi libvirt-daemon Name : libvirt-daemon Version : 6.0.0 Release : 13.13.1 Architecture: x86_64 Install Date: Tue Jun 8 08:20:30 2021 ... Regards, Ulrich > I wonder: Is there a way to prevent stop/start migration if live‑migration > failed? > In out case the migration was triggeerd by resource placement strategy. > > The messages logged would look like this: > warning: Unexpected result (error: v15: live migration to h18 failed: 1) > was recorded for migrate_to of prm_xen_v15 on h16 > > Regards, > Ulrich > > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
