[Xen-users] Re: xm save/restore on a vt enabled machine.

[Anthony Liguori <anthony@xxxxxxxxxxxxx>]

Save and restore is not implemented for HVM domains.  The error your
seeing is an attempt to do a paravirtual save on an HVM domain (doh!).  We
could probably have a better error message here.

In theory, save/restore won't be that hard for HVM domains.  Since QEMU
already supports saving/restore the hardware state, adapting that
shouldn't be that hard.

Unfortunately, save/restore hardware support is broken in some of the
devices QEMU emulates right now.  Specifically, I believe USB and the
Cirrus chipsets are both not working properly.

Regards,

Anthony Liguori

On Mon, 10 Jul 2006 17:03:12 -0700, John McCullough wrote:

> Hello,
> 
> I am working with WinXP on xen-unstable and LVM.  I am interested in the
> current status of the xm save/restore functionality.  Currently, using xm
> save results in a failure.
> 
> Using:
> # xm save winxp-snap0 winxp-snap0.save
> 
> I receive on the console:
> Error: /usr/lib/xen/bin/xc_save 10 19 3 0 0 0 failed
> 
> Within xend.log the most relevant portion is: DEBUG (XendCheckpoint:83)
> [xc_save]: /usr/lib/xen/bin/xc_save 10 19 2 0 0 0 ERROR
> (XendCheckpoint:234) Couldn't map p2m_frame_list_list (errno 14): 14 ERROR
> (XendCheckpoint:234) Save exit rc=1 ERROR (XendCheckpoint:106) Save failed
> on domain winxp-snap1 (2).
> 
> errno 14 is Bad Address.
> 
> I have heard that save is broken on VT, and I was wondering whether there
> is any rough timeline and what needs to be fixed.  I also heard that the
> problem may be in Qemu.  Could someone verify whether this is the case?
> 
> Regards,
> John
> 
> p.s. should this have gone to xen-devel?



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