WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] "xm save" trouble -- deadlock?

On Wed, Nov 02, 2005 at 04:35:00PM +0100, Gerd Knorr wrote:

> >I've done a threaded fix already.  You're welcome to have a go at doing it
> >without a thread if you want, but I think it'll be messy.
> 
> Ok, wile waiting for the fix show up in the public mercurial tree I've 
> workarounded the issue with a wrapper script which redirects xc_save 
> stderr to a file.  There I get this:
> 
>    FNI 21 : [10000003,768] pte=25fae063, mfn=00025fae, pfn=00001b00 
> [mfn]=deadbeef
>    FNI 21 : [10000003,769] pte=25faf063, mfn=00025faf, pfn=00001b01 
> [mfn]=deadbeef
>    FNI 21 : [10000003,770] pte=25fb0063, mfn=00025fb0, pfn=00001b02 
> [mfn]=deadbeef
>    [ ... many more of these ... ]
> 
> In the source code there where message is printed I find a comment 
> saying "/* I don't think this should ever happen */".  Hmm.  It does. 
> And probably it is a problem.

In and of itself, this diagnostic message is harmless, despite the comment to
the contrary.

> "xm save" works now, but I can't restore the domain:
> 
>   master-xen root /tmp# xm restore /vm/ttylinux/suspend.img
>   Error: Could not read store/console MFN

It is trying to read two values that are output by the xc_restore helper
program on its stdout.  Have you inadvertently lost xc_restore's stdout?  If
not, then xc_restore is broken -- check for corresponding diagnostic
information in /var/log/xend.log, /var/log/xend-debug.log, and dmesg.

Ewan.

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