From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Knorr Subject: Re: "xm save" trouble -- deadlock? Date: Wed, 02 Nov 2005 18:23:58 +0100 Message-ID: <4368F62E.6010402@suse.de> References: <43679B4C.3030804@suse.de> <4367A2AF.2090707@suse.de> <20051101185456.GA21507@leeni.uk.xensource.com> <43688610.2010601@suse.de> <20051102100429.GA408@leeni.uk.xensource.com> <4368DCA4.6000709@suse.de> <20051102154103.GC408@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20051102154103.GC408@leeni.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: xen-devel List-Id: xen-devel@lists.xenproject.org >> "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. Well, depends on at which point in time I suspend the ttylinux Domain. When suspending it quickly, so I catch it during kernel boot, suspend and resume works ok. The resumed domain quickly stops though and starts eating CPU time. I also see the mfn messages in the stdout logfile when starting xc_restore using the logging wrapper script. When suspending it once it bootet to the login prompt the resume doesn't work. The stdout log also is empty. BTW: what is the latest linux kernel code? Ian announced linux-2.6-xen.hg some weeks ago and also mentioned the sparse trees in the xen-unstable.hg repository will be kept in sync. Is that still the case? cheers, Gerd