Re: [Xen-devel] [Planning for Xen-4.6] Migration v2

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2014-11-25 at 19:54 +0000, Andrew Cooper wrote:
> 3) Libxl and xl support
> 
> Libxl and xl have as many problems as the libxc code did when it comes
> to incompatible wire formats and layering violations.  In particular, it
> is not possible to determine the bitness of the sending
> libxl-saverestore-helper, meaning that legacy conversion requires active
> administrator input, or at least a passive assumption that the bitness
> is the same.

IOW when migrating legacy->new we have the same restriction as we do
today in the purely legacy world, which is that the two dom0's must
having match bit widths?

IMHO this is fine. It essentially means that for xl users there is some
delayed gratification wrt the promise of migration between non-alike
dom0s. The migration from 4.5(legacy)->4.6(v2) won't support such
migrations, but the next step from 4.6(v2)->4.7(v2) will.

Ian.


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