On Fri, Feb 21, 2020 at 05:41:58PM +0100, David Hildenbrand wrote: > In case we grow our RAM after ram_postcopy_incoming_init() (e.g., when > synchronizing the RAM block state with the migration source), the resized > part would not get discarded. Let's perform that when being notified > about a resize while postcopy has been advised, but is not listening > yet. With precopy, the process is as following: > > 1. VM created > - RAM blocks are created > 2. Incomming migration started > - Postcopy is advised > - All pages in RAM blocks are discarded > 3. Precopy starts > - RAM blocks are resized to match the size on the migration source. > - RAM pages from precopy stream are loaded > - Uffd handler is registered, postcopy starts listening > 3. Guest started, postcopy running > - Pagefaults get resolved, pages get placed > > Cc: "Dr. David Alan Gilbert" <dgilb...@redhat.com> > Cc: Juan Quintela <quint...@redhat.com> > Cc: Peter Xu <pet...@redhat.com> > Signed-off-by: David Hildenbrand <da...@redhat.com>
Reviewed-by: Peter Xu <pet...@redhat.com> -- Peter Xu
