Re: [Xen-devel] slow live magration / xc_restore on xen4 pvops

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Brendan Cully writes ("Re: [Xen-devel] slow live magration / xc_restore on xen4 
pvops"):
> 2. in normal migration, the sender should close the fd after sending
> all data, immediately triggering an IO error on the receiver and
> completing the restore.

This is not true.  In normal migration, the fd is used by the
machinery which surrounds xc_domain_restore (in xc_save and also in xl
or xend).  In any case it would be quite wrong for a library function
like xc_domain_restore to eat the fd.

It's not necessary for xc_domain_restore to behave this way in all
cases; all that's needed is parameters to tell it how to behave.

> I did try to avoid disturbing regular live migration as much as
> possible when I wrote the code. I suspect some other regression has
> crept in, and I'll investigate.

The short timeout is another regression.  A normal live migration or
restore should not fall over just because no data is available for
100ms.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel