From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: FW: Xen 4.1 interrupts not delievered. Date: Mon, 18 Oct 2010 10:59:24 -0400 Message-ID: <20101018145924.GA27373@dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Lin, Ray" Cc: "jeremy@goop.org" , "xen-devel@lists.xensource.com" , "keir@xen.org" , "bruce.edge@gmail.com" , "Ian.Campbell@eu.citrix.com" , "linux@eikelenboom.it" , "m.a.young@durham.ac.uk" List-Id: xen-devel@lists.xenproject.org On Fri, Oct 15, 2010 at 02:57:44PM -0600, Lin, Ray wrote: > > We experienced the domU interrupt/DMA issue before. The symptom is like the /proc/interrupts/irq# of Tachyon chip (FC controller) keep on incrementing, but nobody is serving the interrupts. Eventually the count of these unserved interrupts reach the max. and are forced to be disabled. With Konrad's dom0/domU configuration, this issue is resolved now. Can you send the old dom0/domU configuration? I am really curious as of why it would work - the configuration for domU was just mostly made minimal to boot a tiny kernel, and the dom0 was based on Ubuntu/Fedora Core 13 and then enabling all of the Xen options.