On Fri, Nov 14, 2014 at 05:59:23PM +0100, Sander Eikelenboom wrote: > > Friday, November 14, 2014, 4:43:58 PM, you wrote: > > >>>> On 14.11.14 at 16:20, <li...@eikelenboom.it> wrote: > >> If it still helps i could try Andrews suggestion and try out with only > >> commit aeeea485 .. > > > Yes, even if it's pretty certain it's the second of the commits, verifying > > this would be helpful (or if the assumption is wrong, the pattern it's > > dying with would change and hence perhaps provide further clues). > > > Jan > > > Ok with a revert of f6dd295 .. it survived cooking and eating a nice bowl of > pasta without a panic. So it would probably be indeed that specific commit.
Thank you for confirmation. Could you give some specifics on the guests? As in what kind of devices you are giving it - and more interestingly - what type of interrupt mechanism do they use (/proc/interrupts along with 'dmesg' | grep <name of driver> should give some ideas). I wouldn't worry about the PV case as that bypasses the dpci codebase - just on the HVM side. Thanks again! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
