[Xen-devel] xm save workaround

[John Croft <john@xxxxxxxxxxxxxxxx>]

Hi all,

This is something I posted earlier on Xen-Users. I understand it is a known 
problem so you may be interested in this workaround.

cheers,
John


Hi John-

Thanks a lot, that did the trick.  Have you sent this to the Xen-Devel
list?  If not, I bet they would be interested.

Anyway, thanks again!

-Patrick

On 3/24/06, John Croft <john@xxxxxxxxxxxxxxxx> wrote:

> > Hi Patrick,
> >
> > I'm wondering if this is related to the problem I had and posted on the
> > xen-users list with a work-around. The symptoms are similar in that
> > xm_save fails but the debug output is slightly different, but that may
> > be due to environmental differences.
> >
> > original post follows.
> > John
> >
> > Hi all,
> >
> > Just installed Xen from the base FC5 released on Monday.
> >
> > It all seems to work great except for "xm save/migrate" which fails with
> > "Unable to get platform info.: 9" at XendCheckpoint:227.
> >
> > Playing around with it I found that there is a program called xc_save
> > which is called from XendCheckpoint.py and passed in a file handle for
> > the xend session and the target file named on the command line. These
> > handles seem to be closed when xc_save exec's, so subsequent calls into
> > Xen by xc_save fail. I got it to work by adding...
> >
> >    from fcntl import ioctl;
> >    FIONCLEX = 0x5450
> >
> > near the top of XendCheckpoint.py
> >
> > and...
> >
> >    ioctl (fd, FIONCLEX, 0)
> >    ioctl (xc.handle(), FIONCLEX, 0)
> >
> > at the beginning of forkHelper.
> >
> > I'm presuming that there are people in the world that this program works
> > for!!! So am I missing a python config item somewhere? Or what am I
> > doing wrong that I need this incantation ?
> >
> > thanks
> > John
> >
> >
> > Patrick Kaeding wrote:
>  
>
> > > >Jamie-
> > > >
> > > >I hope you don't mind that I am copying the Xen-Users mailing list on
> > > >this, in the hope others will see it also.
> > > >
> > > >Yes, I am still having this problem.  I believe it is caused by a bug
> > > >somewhere in the Xen code, which breaks the save functionality.  This
> > > >then means the live migration also doesn't work, since that depends on
> > > >save.
> > > >
> > > >I believe the developers are aware of this problem, and are working on
> > > >a solution, but maybe someone else can shed more light on the current
> > > >situation.
> > > >
> > > >Thanks,
> > > >Patrick
> > > >
> > > >On 3/24/06, jamie chapman <jamiechap@xxxxxxxxx> wrote:
> > > >
> > > >
> >    
> >
> > > > >>Hello Mr Kaeding, how are you.
> > > > >>
> > > > >>After reading the XenSource mailing list, i at long last came across
> > > > >>someone that had the same problem as myself.
> > > > >>
> > > > >>I am relatively new to the game so plaese excuse me if i seem foolish.
> > > > >>
> > > > >>I am running 2 Xeon Dual Core, with 1 Gig of RAM. Using SuSE 10.0 and
> > > > >>Xen 3.0(8259) installed and seems to work fine, creating, destroying
> > > > >>domains. The problem is when i try to save the guest domain using, xm
> > > > >>save guestName guest.chk
> > > > >>
> > > > >>It returns with /usr/lib/xen/bin/xc_save 11 17 1 0 0 0 failed
> > > > >>
> > > > >>The addition to xend.log after i call xm save is
> > > > >>(XendCheckpoint:227)  Couldnt map p2m_frame_list_list (errno14): 14
> > > > >>(XendCheckpoint:227)  Save xeit rc=1
> > > > >>(XendCheckpoint:227)  Save failed on domain guest (18).
> > > > >>
> > > > >>
> > > > >>Any info from you would be greatly appreciated.
> > > > >>
> > > > >>Thanks a lot, Jamie..
> > > > >>
> > > > >>
> > > > >>
> > >      
> > >
> > > >
> > > >_______________________________________________
> > > >Xen-users mailing list
> > > >Xen-users@xxxxxxxxxxxxxxxxxxx
> > > >http://lists.xensource.com/xen-users
> > > >
> > > >
> >    
>  
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel