Am Wed, 10 Apr 2019 17:25:04 +0100
schrieb Anthony PERARD :
> Because "Snapshots don't need to inactivate images", see:
> https://lists.xenproject.org/archives/html/xen-devel/2017-10/msg02782.html
>
> I had to add the `live' parameter to fix the lock issue.
Thanks, I will double check this
On Mon, Jan 07, 2019 at 11:07:43AM +0100, Olaf Hering wrote:
> Am Fri, 4 Jan 2019 17:48:31 +0100
> schrieb Olaf Hering :
>
> > Am Fri, 4 Jan 2019 16:57:55 +0100
> > schrieb Olaf Hering :
> >
> > > worth keeping (and fixing) the concept of an "offline migration"
> >
> > And regarding the fix,
Anthony,
looks like this fix missed qemu-4.0.
What is your opinion on this fix? I think there was zero reply...
Olaf
On Mon, Jan 07, Olaf Hering wrote:
> Am Fri, 4 Jan 2019 17:48:31 +0100
> schrieb Olaf Hering :
>
> > Am Fri, 4 Jan 2019 16:57:55 +0100
> > schrieb Olaf Hering :
> >
> > >
Am Fri, 4 Jan 2019 17:48:31 +0100
schrieb Olaf Hering :
> Am Fri, 4 Jan 2019 16:57:55 +0100
> schrieb Olaf Hering :
>
> > worth keeping (and fixing) the concept of an "offline migration"
>
> And regarding the fix, it looks like qmp_xen_save_devices_state does not need
> the concept of
Am Fri, 4 Jan 2019 16:57:55 +0100
schrieb Olaf Hering :
> worth keeping (and fixing) the concept of an "offline migration"
And regarding the fix, it looks like qmp_xen_save_devices_state does not need
the concept of "live". Just shutdown the blockdevices and be done with it?
+++
With 'xl migrate' the migration is always live, while 'virsh migrate' will do
an offline migration unless '--live' is used. Such non-live migration will
break with HVM because the sending side does not seem to unlock the qcow2 image.
I wonder if its worth keeping (and fixing) the concept of an
