Re: Memory locking limit and zero-copy migrations

On Fri, Aug 19, 2022 at 08:01:58 +0200, Milan Zamazal wrote: > Fangge Jin writes: > > > On Fri, Aug 19, 2022 at 4:08 AM Milan Zamazal wrote: > > > >> > Not sure whether you already know this, but I had a hard time > >> > differentiating the two concepts: > >> > 1. memlock hard limit(shown by prl

Re: Memory locking limit and zero-copy migrations

Fangge Jin writes: > On Fri, Aug 19, 2022 at 4:08 AM Milan Zamazal wrote: > >> > Not sure whether you already know this, but I had a hard time >> > differentiating the two concepts: >> > 1. memlock hard limit(shown by prlimit): the hard limit for locked host >> > memory >> > 2. memtune hard limi

Re: Memory locking limit and zero-copy migrations

On Fri, Aug 19, 2022 at 4:08 AM Milan Zamazal wrote: > > Not sure whether you already know this, but I had a hard time > > differentiating the two concepts: > > 1. memlock hard limit(shown by prlimit): the hard limit for locked host > > memory > > 2. memtune hard limit(memtune->hard_limit): the h

Re: Memory locking limit and zero-copy migrations

Fangge Jin writes: > On Thu, Aug 18, 2022 at 2:46 PM Milan Zamazal wrote: > >> Fangge Jin writes: >> >> > 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 star

Re: Memory locking limit and zero-copy migrations

On Thu, Aug 18, 2022 at 2:46 PM Milan Zamazal wrote: > Fangge Jin writes: > > > 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 wil

Re: Memory locking limit and zero-copy migrations

Fangge Jin writes: > 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->ha

Re: Memory locking limit and zero-copy migrations

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 memtune

Re: Memory locking limit and zero-copy migrations

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,

Re: Memory locking limit and zero-copy migrations

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? >

Re: Memory locking limit and zero-copy migrations

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 "pr

Memory locking limit and zero-copy migrations

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 QEMU