[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Xen-devel] [PATCH] migration, xen: Fix block image loc
|
From: |
Anthony PERARD |
|
Subject: |
Re: [Qemu-devel] [Xen-devel] [PATCH] migration, xen: Fix block image lock issue on live migration |
|
Date: |
Tue, 3 Oct 2017 12:47:43 +0100 |
|
User-agent: |
Mutt/1.9.1 (2017-09-22) |
On Tue, Oct 03, 2017 at 12:33:37PM +0100, Roger Pau Monné wrote:
> On Mon, Oct 02, 2017 at 04:30:58PM +0000, Anthony PERARD wrote:
> > When doing a live migration of a Xen guest with libxl, the images for
> > block devices are locked by the original QEMU process, and this prevent
> > the QEMU at the destination to take the lock and the migration fail.
> >
> > From QEMU point of view, once the RAM of a domain is migrated, there is
> > two QMP commands, "stop" then "xen-save-devices-state", at which point a
> > new QEMU is spawned at the destination.
> >
> > Release locks in "xen-save-devices-state" so the destination can takes
> > them.
>
> What happens if the migration fails on the destination? Will QEMU pick
> the lock again when resuming on the source in this case?
Yes, calling the QMP command "cont" to resume the activity makes QEMU
take the lock again, and libxl would call "cont". (I don't think you can
pick this kind of lock ;-). )
--
Anthony PERARD