xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: xen-devel@lists.xenproject.org,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH] migration, xen: Fix block image lock issue on live migration
Date: Wed, 29 Nov 2017 15:06:19 +0000	[thread overview]
Message-ID: <20171129150619.GD2004@perard.uk.xensource.com> (raw)
In-Reply-To: <bf0e06f5-13b4-cbef-4a00-f1f61a3c262e@linaro.org>

On Wed, Nov 29, 2017 at 12:28:39PM +0000, Julien Grall wrote:
> + Stefano
> 
> On 11/27/2017 03:00 PM, Anthony PERARD wrote:
> > Hi Julien,
> 
> Hi Anthony,
> 
> > 
> > Can I get a release-ack for this patch?
> > 
> > This fix local live migration of HVM guest when the disk backend is
> > qdisk.  osstest doesn't report a regression because the kernel or the
> > glibc is just a bit too old.
> 
> When does that regression happen? I am considering to release Xen 4.10 soon
> and would need more details to decide the inclusion of the patch.

That can happen when an API call Open File Description Locks
(F_OFD_GETLK and F_OFD_SETLK) is available. There are since Linux 3.15
and glibc 2.20.

When this API is available, QEMU is going to set a lock on the file open
for a block device. When we try to live migrate a guest and the lock is
set, the new QEMU is going to fail to open the disk with an error
message that say something like "file locked", and migration fail.

The scenario when the lock is an issue are:
- an HVM guest which us qdisk for disk backend. (Like when the disk
  image is in a format different than raw. e.g. qcow2)
- an HVM guest which only use emulated disk.


BUT I can't reproduce the issue with the QEMU we are going to release...
so there is probably a race involve. I guess the patch can wait.

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2017-11-29 15:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171122084504.11984-1-quintela@redhat.com>
     [not found] ` <20171122084504.11984-2-quintela@redhat.com>
2017-11-27 15:00   ` [PATCH] migration, xen: Fix block image lock issue on live migration Anthony PERARD
2017-11-29 12:28     ` Julien Grall
2017-11-29 15:06       ` Anthony PERARD [this message]
2017-12-01 16:17         ` Julien Grall
2017-10-02 16:30 Anthony PERARD
2017-10-02 19:18 ` Dr. David Alan Gilbert
2017-10-04 13:03   ` Kevin Wolf
2017-10-24 12:11     ` Anthony PERARD
2017-10-03 11:33 ` Roger Pau Monné
2017-10-03 11:47   ` Anthony PERARD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171129150619.GD2004@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).