Re: [libvirt] [PATCH 3/3] qemu: Adjust max memlock on mdev hotplug

2019-09-09 Thread Pavel Hrdina
On Tue, Sep 03, 2019 at 10:09:48PM +0200, Eric Farman wrote: > When starting a domain, we use the presence of a vfio-pci or > mdev hostdev to determine if the memlock maximum needs to be > increased. But if we hotplug either of these devices, only the > vfio-pci path gets that love. This means

Re: [libvirt] [PATCH 3/3] qemu: Adjust max memlock on mdev hotplug

2019-09-06 Thread Daniel Henrique Barboza
On 9/3/19 5:09 PM, Eric Farman wrote: When starting a domain, we use the presence of a vfio-pci or mdev hostdev to determine if the memlock maximum needs to be increased. But if we hotplug either of these devices, only the vfio-pci path gets that love. This means that attaching a, say,

[libvirt] [PATCH 3/3] qemu: Adjust max memlock on mdev hotplug

2019-09-03 Thread Eric Farman
When starting a domain, we use the presence of a vfio-pci or mdev hostdev to determine if the memlock maximum needs to be increased. But if we hotplug either of these devices, only the vfio-pci path gets that love. This means that attaching a, say, vfio-ccw device will appear to succeed but the