From: Anthony PERARD <anthony.perard@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xen.org
Subject: Re: migration regression in xen-4.11 and qemu-2.11 and qcow2
Date: Thu, 10 May 2018 11:40:18 +0100 [thread overview]
Message-ID: <20180510104018.GA2057@perard.uk.xensource.com> (raw)
In-Reply-To: <20180508133143.77e209f2.olaf@aepfle.de>
On Tue, May 08, 2018 at 01:31:43PM +0200, Olaf Hering wrote:
> It is unclear why that was never noticed in xen-4.10, qemu-2.9 did not have that bug.
> Also, if a KVM or Xen guest is migrated should make zero difference for the qcow2 driver...
Hi Olaf,
I did try to fix a migration related issue that has to do with a new
lock placed by qemu. But if the issue your having is actually fixed.
The lock as been introduced in QEMU 2.10, but the was not working well
with Xen, so for Xen 4.10, I've apply to qemu-xen-4.10:
migration, xen: Fix block image lock issue on live migration
a4166a0a50dda967f30c9d85fa8aa2ea2539798e
I did fix the bug in QEMU 2.11 (5d6c599fe1d69a1bf8c5c4d3c58be2b31cd625ad)
so Xen 4.11 does include it it the qemu-xen tree.
There is one last commit for libxl:
libxl_qmp: Tell QEMU about live migration or snapshot
db0c7dde021c29c2ae0d847d70fb7b59e02ea522
I'm not sure if that information is going to help, but that what I have
for now about the lock of block images.
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-05-10 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 15:19 migration regression in xen-4.11 and qemu-2.11 and qcow2 Olaf Hering
2018-05-08 11:31 ` Olaf Hering
2018-05-08 16:40 ` Olaf Hering
2018-05-09 12:23 ` Olaf Hering
2018-05-09 21:08 ` Stefano Stabellini
2018-05-09 21:13 ` Olaf Hering
2018-05-09 21:43 ` Stefano Stabellini
2018-05-10 6:04 ` Olaf Hering
2018-05-10 16:03 ` Stefano Stabellini
2018-05-16 13:13 ` Olaf Hering
2018-05-10 10:40 ` Anthony PERARD [this message]
2018-05-14 14:15 ` Olaf Hering
2018-05-16 14:53 ` Olaf Hering
2018-05-17 6:30 ` Olaf Hering
2018-05-17 9:08 ` Olaf Hering
2018-05-17 8:31 ` Olaf Hering
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=20180510104018.GA2057@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xen.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).