Description of problem:

vfio manages user locked pages on a per container basis.  Containers represent an address space for a device.  When a viommu is not present, all assigned devices in a VM share the same address space and therefore share the same container.  In this mode, the locked memory limits of the QEMU process generally matches the overall RAM configured for the VM.

When a viommu is configured for the VM, whether disabled or in passthrough mode, each assigned device has its own address space and is therefore configured within its own container.  In passthrough mode, the address space for each container is required to map the full VM, therefore the locked memory requirements increase to the full VM address space PER assigned device.

If we intend to make viommu a default configuration, this increase in locked memory needs to be addressed, either by enlightening management tools to multiply the locked memory limit by the number of assigned devices or changing the vfio APIs to be able to associate multiple containers to the same user process and avoid duplicate accounting.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: