[libvirt] [PATCH 1/8] Revert "qemu: Forbid <memoryBacking><locked> without <memtune><hard_limit>"

[Luiz Capitulino]

On Mon, 27 Mar 2017 10:33:52 +0200
Andrea Bolognani <abologna at redhat.com> wrote:

> On Fri, 2017-03-24 at 13:36 -0400, Luiz Capitulino wrote:
> > > Turns out this check is excessively strict: there are ways
> > > other than <memtune><hard_limit> to raise the memory locking
> > > limit for QEMU processes, one prominent example being
> > > tweaking /etc/security/limits.conf.  
> > 
> > Actually, it seems that limits.conf doesn't work with libvirt
> > as mentioned by Daniel in another thread. I didn't know this
> > myself btw.
> > 
> > This makes this series even more important because only through
> > libvirt we can set this limit to infinity.  
> 
> Well, it *does* work if you set it up properly, eg. raise the
> memory locking limit for the user under which libvirtd will
> run instead of the user under which QEMU processes will run.

Doesn't libvirtd run as root?

> 
> Doing so is very counter-intuitive, though.
> 
> -- 
> Andrea Bolognani / Red Hat / Virtualization
>