From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: XEN 4.0 + 2.6.31.13 pvops kernel : system crashes on starting 155th domU Date: Wed, 28 Apr 2010 01:43:50 +0100 Message-ID: References: <019701cae5dd$01b36e70$051a4b50$@ucsd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <019701cae5dd$01b36e70$051a4b50$@ucsd.edu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Yuvraj Agarwal , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 27/04/2010 08:41, "Yuvraj Agarwal" wrote: > Attached is the output of /var/log/daemon.log and /var/log/xen/xend.log, = but > as far as we can see we don=B9t quite know what might be going causing the > system to crash (no console access anymore and system becomes unresponsiv= e and > needs to be power-cycled). I have pasted only the relevant bits of > information (the last domU that did successfully start and the next one t= hat > failed). It may be the case that all the log messages weren=B9t flushed bef= ore > the system crashed=8A > =20 > Does anyone know where this limit of 155 domU is coming from and how we c= an > fix/increase it?=20 Get a serial line on a test box, and capture Xen logging output on it. You can both see if any crash messages come from Xen when the 155th domain is created, and also try the serial debug keys (e.g., try 'h' to get help to start with) to see whether Xen itself is still alive. -- Keir