From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: 4.1.1 dom0 kernel panic "No available IRQ to bind to: increae nr_irqs!" Date: Mon, 22 Aug 2011 16:59:18 -0400 Message-ID: <20110822205917.GA24557@dumpdata.com> References: <4E52BA6E.5000409@gt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4E52BA6E.5000409@gt.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Nathan March Cc: "Xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Mon, Aug 22, 2011 at 01:22:06PM -0700, Nathan March wrote: > Hi, > > I've run into an issue where after spawning more than ~22 VMs, the dom0 > will panic with: > > Kernel panic - not syncing: No available IRQ to bind to: increase nr_irqs! > > xen7 ~ # dmesg | grep IRQ > [ 40.430664] NR_IRQS:4352 nr_irqs:512 > > This is on xen 4.1.1 with the 2.6.32.43 kernel from jeremy xen.git. > > I do have sparse IRQ's on: > CONFIG_SPARSE_IRQ=y > > I've found numerous comments about this online, but they primarily seem > to apply to earlier versions of xen. More recent comments seem to > indicate it shouldn't be a problem since the IRQ's are dynamically > increased? The kernel doesn't seem to have NR_IRQS specified anywhere Not that version of kernel. > that I can see... > > Can anyone point me in the right direction to resolve this? Update the kernel to 3.0. We added a lot of fixes to make the IRQ dynamic so that you can have as many IRQs as much as there is memory to allocate them. > > Thanks, > Nathan > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel