RE: [Xen-users] Dom0 and Domu sharing a physical IRQ results ineventual crash

["[STD]Ein" <ein@xxxxxxxxxxxxxx>]

As previously discussed in the list, adding noirqdebug to your dom0 kernel line *may* solve the issue.  However, don’t get your hopes too high, as sharing irq’s across domains is problematic at best.  Your best bet is to try enabling any apic/ioapic options in the bios, as this may reduce/eliminate irq sharing.  Again, that is a may, both of the machines that I have available to me (two different chipsets) create identical irq maps regardless, but your mileage may vary.

 

---

From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Christopher Isip
Sent: June 9, 2008 9:35 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Dom0 and Domu sharing a physical IRQ results ineventual crash

 

I have one xen machine  where dom0 libata and pcibacked domU eth0 share a physical IRQ.  I thought that the disk was bad (cause the system was crashing and giveing me disk errors) and replaced it with an IDE disk connected to a pcibacked SATA-IDE combo card.  Problem seems to have gone away.  The machine runs stably and hasn't crashed yet.

Now I have another machine where I pciback usb.  The usb port in domU shares a physical irq with the dom0 libata.  The machine crashes every few hours with disk errors.   In the domU, I see usb related errors as well (usblp removed, etc.). 

Is there anyway to prevent the irq sharing?  I think this is the cause of the crash.

Thanks
Chris

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