RE: [Xen-devel] Live Migration Error

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

> Teemu saves the day!!!
> I actually set the timeout to 100 for no particular reason 
> (originally it was 10, 20 didn't work either) Thanks Ian for 
> your suggestion as well

I'd be really surprised if increasing the timeout actually made a difference. 
Are you sure you're not just using the shadow mode fix that was checked in a 
couple of hours ago?

Best,
Ian

> Cheers!!
> Andres
> At 02:45 PM 5/13/2005, Teemu Koponen wrote:
> >On May 13, 2005, at 20:07, Andres Lagar Cavilla wrote:
> >
> >Andres,
> >
> >>I try to do a live migration in the same physical host, i.e. xm 
> >>migrate --live 'whatever' localhost It fails with 'Error: errors: 
> >>suspend, failed, Callbak timed out'.
> >>It seems like transfer of memory pages works until the 
> point when the 
> >>domain needs to be suspended to do the final transfer. 
> Funny thing is 
> >>it used to work before, gloriously, and I haven't made any 
> >>software/hardware changes. At some point a xm save command 
> failed with 
> >>timeout, and from there on live migration fails with this message. 
> >>Non-live migration works perfectly, also between different physical 
> >>hosts. save/restore also works flawlessly.
> >
> >I had similar timeout errors previously, when I was using a 
> bit slower 
> >servers. I overcame the problem by slightly increasing the timeout 
> >value in controller.py. It seemed to provide a remedy.
> >
> >Teemu
> >
> >--
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

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