Hello, On Fri, Apr 1, 2016 at 3:34 PM, Julien Grall <julien.gr...@arm.com> wrote: > Hello Dushyant, > > On 29/03/16 21:56, Dushyant Behl wrote: >> >> On Wed, Mar 30, 2016 at 12:31 AM, Julien Grall <julien.gr...@arm.com> >> wrote: >>> >>> On 24/03/16 11:05, Dushyant Behl wrote: > > >> (XEN) DOM0: [ 0.000000] irq: no irq domain found for >> /interrupt-controller ! >> (XEN) DOM0: [ 0.000000] irq: no irq domain found for >> /interrupt-controller ! >> (XEN) DOM0: [ 0.000000] irq: no irq domain found for >> /interrupt-controller ! >> (XEN) DOM0: [ 0.000000] arch_timer: No interrupt available, giving up > > > It looks like to me that Xen is not recreating the device-tree correctly. I > would look into the kernel to find what is expected.
This looks like a possible bug (or some missing feature) in Xen's device tree creation which could take some time to handle, so if I could be of any more help to you with this issue please let me know. [I've cc'ed Ian Campbell in this mail (Sorry for cc'ing you explicitly)] Ian, Actually, I want to run Xen on the Tegra Jetson board for some project of mine but currently Linux-4.1 is failing as dom0 because its not able to receive interrupts from the arch_timer. This link contains the dom0 failure boot log - http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg03715.html In your patch for *Hacky* support for Jetsok-TK1 you said that you were able to run guests on Jetson-tk1 board with Xen. Can I know which kernel version you used as dom0 (and possibly domU guests)? Thanks and Regards, Dushyant Behl _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel