The call to setrlimit should be from qemuDomainAdjustMaxMemLock->virProcessSetMaxMemLock
And it has a pid switch:
0 - increase the global limit via setrlimit
<pid> increase the limit of a process via prlimit
That should have a pid set in our case, then use prlmit and thereby work to actually increase the limit we need. I'll continue debugging in that in log&gdb to see where this is coming from and why we don't have a vm-pid.
The call to setrlimit should be from qemuDomainAdjus tMaxMemLock- >virProcessSetM axMemLock
And it has a pid switch:
0 - increase the global limit via setrlimit
<pid> increase the limit of a process via prlimit
That should have a pid set in our case, then use prlmit and thereby work to actually increase the limit we need. I'll continue debugging in that in log&gdb to see where this is coming from and why we don't have a vm-pid.