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

[Xen-users] Re: Xen 3.2 with shared IRQs


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Ben Holt" <beanjammin@xxxxxxxxx>
  • Date: Sat, 9 Feb 2008 09:58:25 -0800
  • Delivery-date: Sat, 09 Feb 2008 09:59:03 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=m0z8zx32phYKkEywaRcT0znCdB8/JoTfVBrJMEIBCmNwvHndVO3hNsqgRUjMFioi5wYcDtlsi8jx7O2RJKEsfgNr/5H17ZPwSQzYH7f1ISu48JsXC5pdgDpROONlMUJ5ZrpUe3qY06u40+iI+LQ2AOrIdRrVDImSY6ox9tNbAsc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 07/02/2008, Ben Holt <beanjammin@xxxxxxxxx> wrote:
> Is "noirqdebug" still the best way to deal with IRQs that are shared
> between hardware in the dom0 and hardware that has been passed to
> domUs?

Just to follow up on my own post in case it helps anyone else, a
couple days after adding "noirqdebug" to the kernel line of my Xen 3.2
dom0 and the "extra" line of the affected domUs I have been crash
free.  Previously IRQ sharing between the IDE interfaces on the dom0
and various hardware passed to a couple domUs had been causing
interrupt problems with the IDE interfaces that would bring down the
domO.

- Ben

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


 


Rackspace

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