Re: [Qemu-devel] Postcopy failures

["Dr. David Alan Gilbert" <dgilbert@redhat.com>]

* Gary Hook (gary.hook@nimboxx.com) wrote:
> I see this went by:
> 
> Il 07/10/2014 12:29, Dr. David Alan Gilbert ha scritto:
> > You mean something like this (untested) ?
> >
> >   if (mis->postcopy_ram_state != POSTCOPY_RAM_INCOMING_NONE) {
> >       if (mis->postcopy_ram_state == POSTCOPY_RAM_INCOMING_ADVISE) {
> >           /*
> >            * Where a migration had postcopy enabled (and thus went to advise)
> >            * but managed to complete within the precopy period
> >            */
> >           postcopy_ram_incoming_cleanup(mis);
> >       } else if (ret >= 0) {
> >            /*
> >             * Postcopy was started, cleanup should happen at the end of the
> >             * postcopy thread.
> >             */
> >            DPRINTF("process_incoming_migration_co: exiting main branch");
> >            return;
> >       }
> >   }
> 
> And I wonder if this will solve the problem of a peer-to-peer migration, using non-shared storage, failing because it appears to take a bit too lon? I see in other threads Dr. Gilbert is making changes related to post copy and I am very interested in getting resolution to what appears to be a timeout problem.
> 
> Any comments would be appreciated by this newbie to Qemu.

It should be possible to postcopy block storage as well, if that's
the question (it might take some work to make sure that they play
nicely together; e.g. wanting to making the page transfer higher
priority than block transfer).
However, I thought there were other ways to do block storage
migration  (using blockcopy I think? but I'm not a block guy).

Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK