WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] 4.1.1 dom0 kernel panic "No available IRQ to bind to: in

To: Nathan March <nathan@xxxxxx>
Subject: Re: [Xen-devel] 4.1.1 dom0 kernel panic "No available IRQ to bind to: increae nr_irqs!"
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 22 Aug 2011 16:59:18 -0400
Cc: "Xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 22 Aug 2011 14:02:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E52BA6E.5000409@xxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4E52BA6E.5000409@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>