On 3/8/21 11:52 AM, Daniel P. Berrangé wrote:
On Fri, Mar 05, 2021 at 08:14:02PM +0100, Andrea Bolognani wrote:
This will be useful when libvirtd is running in a containerized
environment with limited capabilities, and in order to make
things like VFIO device assignment still work an external
On Mon, Mar 08, 2021 at 01:56:15PM +0100, Andrea Bolognani wrote:
> On Mon, 2021-03-08 at 10:52 +, Daniel P. Berrangé wrote:
> > On Fri, Mar 05, 2021 at 08:14:02PM +0100, Andrea Bolognani wrote:
> > > +# If enabled, libvirt will not attempt to change process limits (as
> > > +# configured with
On Mon, 2021-03-08 at 10:52 +, Daniel P. Berrangé wrote:
> On Fri, Mar 05, 2021 at 08:14:02PM +0100, Andrea Bolognani wrote:
> > +# If enabled, libvirt will not attempt to change process limits (as
> > +# configured with the max_processes, max_files and max_core settings
> > +# below) itself
On Fri, Mar 05, 2021 at 08:14:02PM +0100, Andrea Bolognani wrote:
> This will be useful when libvirtd is running in a containerized
> environment with limited capabilities, and in order to make
> things like VFIO device assignment still work an external
> privileged process changes the limits from
On 3/5/21 8:14 PM, Andrea Bolognani wrote:
This will be useful when libvirtd is running in a containerized
environment with limited capabilities, and in order to make
things like VFIO device assignment still work an external
privileged process changes the limits from outside of the
container.
This will be useful when libvirtd is running in a containerized
environment with limited capabilities, and in order to make
things like VFIO device assignment still work an external
privileged process changes the limits from outside of the
container. KubeVirt is an example of this setup.
