From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Hongyang Yang <yanghy@cn.fujitsu.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Wen Congyang <wency@cn.fujitsu.com>,
Xen-devel List <xen-devel@lists.xen.org>
Subject: Request a freeze exception for Libxl Migration v2 in 4.6
Date: Mon, 13 Jul 2015 18:03:09 +0100 [thread overview]
Message-ID: <55A3EF4D.80605@citrix.com> (raw)
Hello,
I would like to request a freeze exception for libxl migration v2.
v3 of the series was posted this morning, and review seems to indicate
that it is mostly on track. I hope to have v4 ready to post tomorrow,
and hope to have no further adjustments required.
On the testing side of things, libxc migration v2 and (an earlier
version of) the python conversion script have shipped in XenServer 6.5.
We are entirely confident of the quality here, have extensive testing in
place.
The libxl side is admittedly far less tested. All testing is so far
manual on my behalf, but I have specifically tested PV (32 and 64), HVM
(qemu trad and upstream) save, restore, and migrate, including inline
legacy->v2 conversion.
The biggest risk, feature wise, is the subject of Remus streams which I
am unable to test. An earlier version of the series had some testing
and identified an issue, which has subsequently been fixed.
~Andrew
next reply other threads:[~2015-07-13 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 17:03 Andrew Cooper [this message]
2015-07-14 10:31 ` Request a freeze exception for Libxl Migration v2 in 4.6 Ian Jackson
2015-07-14 14:00 ` Wei Liu
2015-07-14 14:16 ` Ian Jackson
2015-07-14 14:31 ` Wei Liu
2015-07-14 14:13 ` Ian Jackson
2015-07-14 14:26 ` Wei Liu
2015-07-15 0:53 ` Yang Hongyang
2015-07-15 3:35 ` Yang Hongyang
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=55A3EF4D.80605@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.org \
--cc=yanghy@cn.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.