Re: [libvirt] [PATCH 0/3] Fix memlock limit during hotplug of mdev devices

On 9/6/19 10:29 AM, Daniel Henrique Barboza wrote: > Hi, > > > I've thought about the issue you're fixing. Have you considered/tried > to handle the MemLockLimit upper in the call hierarchy with your new > qemuDomainAdjustMaxMemLockHostdev() function? Both > qemuDomainAttachMediatedDevice() and

Re: [libvirt] [PATCH 0/3] Fix memlock limit during hotplug of mdev devices

Hi, I've thought about the issue you're fixing. Have you considered/tried to handle the MemLockLimit upper in the call hierarchy with your new qemuDomainAdjustMaxMemLockHostdev() function? Both qemuDomainAttachMediatedDevice() and qemuDomainAttachHostPCIDevice() are called from qemuDomainAttachH

[libvirt] [PATCH 0/3] Fix memlock limit during hotplug of mdev devices

The routine qemuDomainGetMemLockLimitBytes() has a couple tests to determine what the maximum limit of locked memory should be. If I start a domain without any vfio stuff, /proc/$PID/limits says the limit is 64KiB. If I start a guest with a vfio-ccw hostdev, the limit is now $GUEST_MEMORY + 1GiB.