[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] 4.1.1 dom0 kernel panic "No available IRQ to bind to: increae nr_irqs!"


  • To: "Xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Nathan March <nathan@xxxxxx>
  • Date: Mon, 22 Aug 2011 13:22:06 -0700
  • Delivery-date: Mon, 22 Aug 2011 13:22:53 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gt.net; h=message-id:date :from:mime-version:to:subject:content-type :content-transfer-encoding; q=dns; s=mail; b=CAEtbGCrg4C9iir2g+t mXZOM/sqGqX9+R03Ka/IrbMlARgn0j6Zuoa55jL8uunS/lpie/7vGOjKWpB4mH4q ccMBoP4M5cstMbrSZSwdQKX5HKu+g5mEukE6T8MOWRfgzI2zcjxbrGgkdeO3grfR 4kMx1EBgnsyyMBpPs6yIZ5lg=
  • List-id: Xen developer discussion <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

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.