On Wed, Aug 03, 2022 at 01:52:41PM +0200, Jiri Denemark wrote: > When we call qemuDomainSetMaxMemLock to reset memory locking limit back > to its original value the domain can already be stopped (for example > after the domain shuts down during migration) in which case it does not > make sense to set any limit. Doing so can even be harmful as we may end > up setting the limit for the daemon itself as the PID is 0. > > Signed-off-by: Jiri Denemark <jdene...@redhat.com> > --- > src/qemu/qemu_domain.c | 4 ++++ > 1 file changed, 4 insertions(+)
Reviewed-by: Pavel Hrdina <phrd...@redhat.com>
signature.asc
Description: PGP signature
