From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Knorr Subject: Re: unstable network trouble Date: Fri, 28 Oct 2005 11:59:47 +0200 Message-ID: <4361F693.3070000@suse.de> References: <4360DCDE.6000207@suse.de> <20051027151234.GX13783@leeni.uk.xensource.com> <4360F5AA.20207@suse.de> <20051027155755.GZ13783@leeni.uk.xensource.com> <4361EA05.2040402@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4361EA05.2040402@suse.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Gerd Knorr Cc: xen-devel , Ewan Mellor List-Id: xen-devel@lists.xenproject.org Hi, >> That one really is odd. Could you post your /var/log/xend.log when that >> happens? > > Attached. The "error: (12, 'Cannot allocate memory')" line looks > strange. [ ... ] Hmm, there seems to be more than one bug. I've manually decreased the amount of memory for domain 0 so there is more free memory, which seems to sucessfully workaround the memory allocation issue. Now I got this one: [2005-10-28 11:55:39 xend.XendDomainInfo] INFO (XendDomainInfo:741) Domain has shutdown: name=debian id=9 reason=reboot. [2005-10-28 11:55:39 xend.XendDomainInfo] ERROR (XendDomainInfo:1278) 1130493287.56 [2005-10-28 11:55:39 xend.XendDomainInfo] DEBUG (XendDomainInfo:1156) XendDomainInfo.destroy: domid=9 [2005-10-28 11:55:39 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164) XendDomainInfo.destroyDomain(9) cheers, Gerd