From: Paul Durrant <Paul.Durrant@citrix.com>
Cc: Olaf Hering <olaf@aepfle.de>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Anthony Perard <anthony.perard@citrix.com>
Subject: Re: live migrating hvm from 4.4 to 4.7 fails in ioreq server
Date: Thu, 12 May 2016 14:13:21 +0000 [thread overview]
Message-ID: <d8e4301d41eb42a69d235185bd09cec8@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20160512141033.GK8063@citrix.com>
> -----Original Message-----
[snip]
> >
> > Ok. Do you regard this as a critical issue for 4.7?
> >
>
> Our general support statement is to support N->N+1 migration, so it is
> not really critical for me. On the other hand, if the fix is not overly
> complex, it would be nice to have for 4.7.
>
> Note that the fix will need to be in upstream QEMU first before it can
> be cherry-picked to our tree, so there is risk that it might just be
> blocked on QEMU side (I haven't checked their schedule). So I wouldn't
> really block xen release just for that.
>
Ok.
> If for some reason (either you don't have time or the patch is blocked
> on QEMU side) the fix doesn't make 4.7.0 I would suggest QEMU maintainer
> to backport to 4.7.1 etc.
>
I'll try to get to it as soon as I can, but my guess is that it will miss 4.7.0.
Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-12 14:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 12:18 live migrating hvm from 4.4 to 4.7 fails in ioreq server Olaf Hering
2016-05-11 12:22 ` Andrew Cooper
2016-05-11 12:30 ` Olaf Hering
2016-05-11 13:07 ` Olaf Hering
2016-05-12 10:53 ` Wei Liu
2016-05-11 12:38 ` Paul Durrant
2016-05-12 10:55 ` Wei Liu
2016-05-12 12:39 ` Paul Durrant
2016-05-12 13:01 ` Wei Liu
2016-05-12 13:03 ` Paul Durrant
2016-05-12 13:18 ` Olaf Hering
2016-05-12 14:10 ` Wei Liu
2016-05-12 14:13 ` Paul Durrant [this message]
2016-05-25 20:57 ` Konrad Rzeszutek Wilk
2016-05-26 8:30 ` Paul Durrant
2016-06-03 20:07 ` Konrad Rzeszutek Wilk
2016-07-26 15:45 ` Olaf Hering
2016-07-26 15:48 ` Paul Durrant
2016-07-29 10:11 ` Paul Durrant
2016-07-29 10:34 ` Paul Durrant
2016-07-29 13:10 ` Olaf Hering
2016-07-29 13:22 ` Paul Durrant
2016-05-12 13:38 ` Stefano Stabellini
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=d8e4301d41eb42a69d235185bd09cec8@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=olaf@aepfle.de \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--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).