Re: "xm save" trouble -- deadlock?

[Gerd Knorr <kraxel@suse.de>]

> 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.  "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

Ideas anyone?  This is a ttylinux instance running out of a ramdisk.

   Gerd