"KSNull Zero" <ksnull01(a)gmail.com&gt; writes: I think it's https://bugzilla.redhat.com/show_bug.cgi?id=1948376, which was fixed in 4.4.6.5. IIRC you need to create links in /etc/pki/vdsm/libvirt-migrate on the source host from server-*.pem to client-*.pem and make sure migrate_tls_x509_verify = 1 is set (it is by default) in /etc/libvirt/qemu.conf. Restarting libvirtd may be needed afterwards. Regards, Milan

"KSNull Zero" <ksnull01(a)gmail.com&gt; writes: Generally no, often yes. Restarting libvirtd shouldn't cause harm to the VMs themselves but it can disrupt running jobs managed by libvirt or confuse oVirt if some actions are being performed at the given moment. It's best to do it when there are no migrations (host migrations don't work for you currently anyway) or other jobs (e.g. snapshots) or actions (e.g. VM startup or shutdown) running on the host. Even if they are, it doesn't necessarily mean something breaks but it's best-effort/no-guarantees workflow instead of the normal workflow. I think just adding the certificate links doesn't require libvirtd restart. And reload may be enough after changing libvirt configuration files.