|
|
|
|
|
|
|
|
|
|
xen-users
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
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-users] Re: xm save,
Patrick Kaeding <=
|
|
|
|
|