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/
Home Products Support Community News


Re: [Xen-devel] Re: CONFIG_SPARSE_IRQ breaks single VCPU domain 0 betwee

To: Erik Brakkee <erik@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: CONFIG_SPARSE_IRQ breaks single VCPU domain 0 between xen/master and xen/next
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Mon, 1 Mar 2010 10:33:17 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 01 Mar 2010 02:34:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <loom.20100228T130046-462@xxxxxxxxxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <1267184533.11737.12277.camel@xxxxxxxxxxxxxxxxxxxxxx> <loom.20100228T130046-462@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sun, 2010-02-28 at 12:01 +0000, Erik Brakkee wrote:
> Ian Campbell <Ian.Campbell <at> citrix.com> writes:
> > 
> > With a single VCPU domain 0 (either due to hardware on dom0_max_vcpus=1)
> > and CONFIG_SPARSE_IRQ on xen/next I see:
> > 
> >         Kernel panic - not syncing: No available IRQ to bind to: increase
> nr_irqs! (currently 256, started from 256)
> > 
> The strange thing is that the kernel panic at boot also appears with 
> xen/master
> now. I am using the .config from
> http://wiki.xensource.com/xenwiki/XenParavirtOps. This behavior is occurring 
> on
> a Sony Vaio F11 laptop (Core i7 720QM, 8GB memory).
> Is there a simple workaround for this problem?

I think the xen/master case is actually down to my "fix off-by-one error
in find_unbound_irq" change -- should probably be reverted.


Xen-devel mailing list

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