Displaying 5 results from an estimated 5 matches for "locklimit".
2019 Aug 22
2
Re: RLIMIT_MEMLOCK in container environment
On Thu, Aug 22, 2019 at 2:24 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> On Wed, Aug 21, 2019 at 01:37:21PM -0700, Ihar Hrachyshka wrote:
> > Hi all,
> >
> > KubeVirt uses libvirtd to manage qemu VMs represented as Kubernetes
> > API resources. In this case, libvirtd is running inside an
> > unprivileged pod, with some host mounts / capabilities
2019 Aug 22
2
Re: RLIMIT_MEMLOCK in container environment
...e this all makes me realize the inanity of adding a <target
> dev='blah' unmanaged='yes'/> for interfaces when hostdevs already have
> <hostdev managed='yes'> and <interface type='hostdev' managed='yes'>. So
> to prevent setting the locklimit for hostdev, would we make a new
> setting like <hostdev managed='no-never-not-even-a-tiny-bit'>? Sigh. I
> *hate* trying to make config consistent :-/)
>
> (alternately, we could just automatically fail the attempt to set the
> lock limit in a graceful manner and allow...
2019 Aug 22
0
Re: RLIMIT_MEMLOCK in container environment
....
(Of course this all makes me realize the inanity of adding a <target
dev='blah' unmanaged='yes'/> for interfaces when hostdevs already have
<hostdev managed='yes'> and <interface type='hostdev' managed='yes'>. So
to prevent setting the locklimit for hostdev, would we make a new
setting like <hostdev managed='no-never-not-even-a-tiny-bit'>? Sigh. I
*hate* trying to make config consistent :-/)
(alternately, we could just automatically fail the attempt to set the
lock limit in a graceful manner and allow the guest to continu...
2019 Aug 24
1
Re: RLIMIT_MEMLOCK in container environment
...the inanity of adding a <target
> >> dev='blah' unmanaged='yes'/> for interfaces when hostdevs already have
> >> <hostdev managed='yes'> and <interface type='hostdev' managed='yes'>. So
> >> to prevent setting the locklimit for hostdev, would we make a new
> >> setting like <hostdev managed='no-never-not-even-a-tiny-bit'>? Sigh. I
> >> *hate* trying to make config consistent :-/)
>
Sounds tough indeed. I'd try to avoid negatively-named knobs. managed=no is
simpler to perceive th...
2019 Aug 22
0
Re: RLIMIT_MEMLOCK in container environment
...akes me realize the inanity of adding a <target
>> dev='blah' unmanaged='yes'/> for interfaces when hostdevs already have
>> <hostdev managed='yes'> and <interface type='hostdev' managed='yes'>. So
>> to prevent setting the locklimit for hostdev, would we make a new
>> setting like <hostdev managed='no-never-not-even-a-tiny-bit'>? Sigh. I
>> *hate* trying to make config consistent :-/)
>>
>> (alternately, we could just automatically fail the attempt to set the
>> lock limit in a grace...