qemu_migration: Don't set unlimited memlock limit for RDMA
qemu_migration: Don't set unlimited memlock limit for RDMA

Our documentation says RDMA migration requires hard_limit to be set so
that we know how big memory locking limit should be set for the domain
during migration. But since commit v1.2.13-71-gcf521fc8ba (which changed
the default hard_limit value from 0 to
VIR_DOMAIN_MEMORY_PARAM_UNLIMITED) we were actually setting memlock
limit to unlimited if hard_limit was not set.

Signed-off-by: Jiri Denemark <62bdf77dc47919a4d59a91822129d14633cfca81@redhat.com>
Reviewed-by: Ján Tomko <4cab11cfb98d3c937327354a78eb07dbb6ee2bc6@redhat.com>

crobinso/libvirt,crobinso/libvirt,olafhering/libvirt,jfehlig/libvirt,olafhering/libvirt,libvirt/libvirt,olafhering/libvirt,libvirt/libvirt,olafhering/libvirt,crobinso/libvirt,zippy2/libvirt,libvirt/libvirt,crobinso/libvirt,zippy2/libvirt,zippy2/libvirt,jfehlig/libvirt,zippy2/libvirt,jfehlig/libvirt,jfehlig/libvirt,libvirt/libvirt