On Thu, Jun 23, 2022 at 16:13:50 +0200, Ján Tomko wrote: > On a Thursday in 2022, Jiri Denemark wrote: > >For RDMA migration we update memory locking limit, but never set it back > >once migration finishes (on the destination host) or aborts (on the > >source host). > > > >Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx> > >--- > > src/qemu/qemu_domain.c | 12 ++++++++++++ > > src/qemu/qemu_domain.h | 3 +++ > > src/qemu/qemu_migration.c | 11 ++++++++--- > > 3 files changed, 23 insertions(+), 3 deletions(-) > > > >diff --git a/src/qemu/qemu_migration.c b/src/qemu/qemu_migration.c > >index fe63f45629..ffae5576d2 100644 > >--- a/src/qemu/qemu_migration.c > >+++ b/src/qemu/qemu_migration.c > >@@ -6410,7 +6415,7 @@ qemuMigrationDstComplete(virQEMUDriver *driver, > > job->apiFlags); > > > > virPortAllocatorRelease(priv->migrationPort); > >- priv->migrationPort = 0; > > This removal is suspicious. Oops, no idea how that happened. Thanks for catching it. Jirka
