Re: [PATCH v3 00/14] File-based migration support and fixed-ram features

2023-03-20 Thread Daniel P . Berrangé
On Mon, Mar 20, 2023 at 12:14:53PM +0100, Claudio Fontana wrote: > (adding Fabiano to the thread) > > On 2/10/23 16:35, Daniel P. Berrangé wrote: > > On Thu, Feb 09, 2023 at 02:32:01PM +0100, Claudio Fontana wrote: > >> Hello Daniel and all, > >> > >> resurrecting this series from end of last year

Re: [PATCH v3 00/14] File-based migration support and fixed-ram features

2023-03-20 Thread Claudio Fontana
(adding Fabiano to the thread) On 2/10/23 16:35, Daniel P. Berrangé wrote: > On Thu, Feb 09, 2023 at 02:32:01PM +0100, Claudio Fontana wrote: >> Hello Daniel and all, >> >> resurrecting this series from end of last year, >> >> do we think that this is the right approach and first step to >> be abl

Re: [PATCH v3 00/14] File-based migration support and fixed-ram features

2023-02-10 Thread Daniel P . Berrangé
On Thu, Feb 09, 2023 at 02:32:01PM +0100, Claudio Fontana wrote: > Hello Daniel and all, > > resurrecting this series from end of last year, > > do we think that this is the right approach and first step to > be able to provide good performance for virsh save and virsh > restore? I've looked thr

Re: [PATCH v3 00/14] File-based migration support and fixed-ram features

2023-02-09 Thread Claudio Fontana
Hello Daniel and all, resurrecting this series from end of last year, do we think that this is the right approach and first step to be able to provide good performance for virsh save and virsh restore? For reference, our previous attempt to get the performance for our use case (libvirt + qemu