On Thu, Aug 18, 2022 at 10:46 AM Fangge Jin wrote:
> I can share some test results with you:
> 1. If no memtune->hard_limit is set when start a vm, the default memlock
> hard limit is 64MB
> 2. If memtune->hard_limit is set when start a vm, memlock hard limit will
> be set to the value of
I can share some test results with you:
1. If no memtune->hard_limit is set when start a vm, the default memlock
hard limit is 64MB
2. If memtune->hard_limit is set when start a vm, memlock hard limit will
be set to the value of memtune->hard_limit
3. If memtune->hard_limit is updated at run-time,
Peter Krempa writes:
> On Wed, Aug 17, 2022 at 10:56:54 +0200, Milan Zamazal wrote:
>> Hi,
>>
>
>> do I read libvirt sources right that when is not used in the
>> libvirt domain then libvirt takes proper care about setting memory
>> locking limits when zero-copy is requested for a migration?
>
On Wed, Aug 17, 2022 at 10:56:54 +0200, Milan Zamazal wrote:
> Hi,
>
> do I read libvirt sources right that when is not used in the
> libvirt domain then libvirt takes proper care about setting memory
> locking limits when zero-copy is requested for a migration?
Well yes, for a definition of
Hi,
do I read libvirt sources right that when is not used in the
libvirt domain then libvirt takes proper care about setting memory
locking limits when zero-copy is requested for a migration?
I also wonder whether there are any other situations where memory limits
could be set by libvirt or
