On Wed, Apr 05, 2017 at 15:09:56 +0200, Jiri Denemark wrote:
> There is no async job running when a freshly started libvirtd is trying
> to recover from an interrupted incoming migration. While at it, let's
> call qemuMigrationResetTLS every time we don't kill the domain. This is
> not strictly
There is no async job running when a freshly started libvirtd is trying
to recover from an interrupted incoming migration. While at it, let's
call qemuMigrationResetTLS every time we don't kill the domain. This is
not strictly necessary since TLS is not supported when v2 migration
protocol is
