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 04:45:09 +0100 Message-ID: References: <004001cae66e$88837cb0$998a7610$@ucsd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <004001cae66e$88837cb0$998a7610$@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 I think nr_irqs is specifiable on the command line on newer kernels. You ma= y be able to do nr_irqs=3D65536 as a kernel boot parameter, or something like that, without needing to rebuild the kernel. -- Keir On 28/04/2010 02:02, "Yuvraj Agarwal" wrote: > Actually, I did identify the problem (don=E2=80=99t know the fix) at least from > the console logs. Its related to running out of nr_irq's (attached JPG > for the console log). >=20 >=20 > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser > Sent: Tuesday, April 27, 2010 5:44 PM > To: Yuvraj Agarwal; xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] XEN 4.0 + 2.6.31.13 pvops kernel : system crashe= s > on starting 155th domU >=20 > On 27/04/2010 08:41, "Yuvraj Agarwal" wrote: >=20 >> Attached is the output of /var/log/daemon.log and /var/log/xen/xend.log, > but >> as far as we can see we don=C2=B9t quite know what might be going causing th= e >> system to crash (no console access anymore and system becomes > unresponsive 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 > that >> failed). It may be the case that all the log messages weren=C2=B9t flushed > before >> the system crashed=C5=A0 >>=20 >> Does anyone know where this limit of 155 domU is coming from and how we > can >> fix/increase it? >=20 > Get a serial line on a test box, and capture Xen logging output on it. Yo= u > 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. >=20 > -- Keir >=20 >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel