xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* 4.1.1 dom0 kernel panic "No available IRQ to bind to: increae nr_irqs!"
@ 2011-08-22 20:22 Nathan March
  2011-08-22 20:59 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 2+ messages in thread
From: Nathan March @ 2011-08-22 20:22 UTC (permalink / raw)
  To: Xen-devel@lists.xensource.com

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
that I can see...

Can anyone point me in the right direction to resolve this?

Thanks,
Nathan

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: 4.1.1 dom0 kernel panic "No available IRQ to bind to: increae nr_irqs!"
  2011-08-22 20:22 4.1.1 dom0 kernel panic "No available IRQ to bind to: increae nr_irqs!" Nathan March
@ 2011-08-22 20:59 ` Konrad Rzeszutek Wilk
  0 siblings, 0 replies; 2+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-08-22 20:59 UTC (permalink / raw)
  To: Nathan March; +Cc: Xen-devel@lists.xensource.com

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-08-22 20:59 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-22 20:22 4.1.1 dom0 kernel panic "No available IRQ to bind to: increae nr_irqs!" Nathan March
2011-08-22 20:59 ` Konrad Rzeszutek Wilk

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).