Re: [Qemu-devel] [PATCH] migration: avoid copying ignore-shared ramblock when in incoming migration

[Peter Maydell]

On Tue, 2 Apr 2019 at 09:57, Catherine Ho <address@hidden> wrote:
> The root cause is the used idx is moved forward after 1st time incoming, and 
> in 2nd time incoming,
> the last_avail_idx will be incorrectly restored from the saved device state 
> file(not in the ram).
>
> I watched this even on x86 for a virtio-scsi disk
>
> Any ideas for supporting 2nd time, 3rd time... incoming restoring?

Does the destination end go through reset between the 1st and 2nd
incoming attempts? I'm not a migration expert, but I thought that
devices were allowed to assume that their state is "state of the
device following QEMU reset" before the start of an incoming
migration attempt.

thanks
-- PMM