Re: [Xen-devel] Migration v2 and related work for 4.6

[Lars Kurth <lars.kurth.xen@xxxxxxxxx>]

We could discuss at the Hackathon next week, and reply to this thread. It seems 
that at least 50% of all the stake-holders are in fact there
Regards
Lars

> On 7 Apr 2015, at 13:00, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:
> 
> On Thu, Apr 02, 2015 at 10:34:34AM +0100, Andrew Cooper wrote:
>> On 02/04/15 10:03, Ian Campbell wrote:
>>> On Wed, 2015-04-01 at 12:03 +0100, Andrew Cooper wrote:
>>>> I propose that the libxc series be accepted independently of the libxl
>>>> series.
>>> That is most likely a good idea IMHO.
>>> 
>>> What do you estimate the chances of the libxl bit being done for 4.6 to
>>> be?
>> 
>> I hope to have everything complete for 4.6, including removal of the
>> legacy code.
>> 
> 
> Not sure what "legacy code" you're referring to, but we definitely want
> to support 4.5 -> 4.6 migration so the "legacy code" might need to stay
> for 4.6?
> 
> Wei.
> 
>> Given the current timescales, I would say most likely.
>> 
>>> 
>>> Is there an option of actually switching to the new libxc without
>>> switching libxl and fixing libxl later, or would that be as much work as
>>> just fixing libxl?
>> 
>> For PV guests, yes.  One can transparently swap the legacy algorithm
>> from the v2 algorithm and every works.
>> 
>> For HVM guests, no.  The handling of the Qemu save record and toolstack
>> records needs fixing.
>> 
>> In the upgrade case, libxl also needs to take care of piping the legacy
>> stream through the conversion script.
>> 
>> ~Andrew
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel