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

Re: [Xen-users] Issues Booting DomU on TI DRA72 Chip

Hi Brandon,

On 08/07/2015 15:36, Brandon Perez wrote:
On 07/08/2015 11:18 AM, Julien Grall wrote:
On 08/07/15 15:07, Brandon Perez wrote:
On 07/08/2015 11:00 AM, Ian Campbell wrote:
On Wed, 2015-07-08 at 09:54 -0400, Brandon Perez wrote:
Pressing Ctrl-o on a xen guest console is the equivalent of the magic
sysrq key, you might find pressing some of those might show what is
going on.

      If I press the sysrq key combinations, while attached to the
with "xl console", Dom0 responds with the appropriate message, but the
DomU guest does not acknowledge the sysrq keys.

If you are logged in via the dom0 console to run xl console to get the
guest console then I think dom0 will eat the Ctrl-o. Not sure if
something like Ctrl-o Ctrl-o will work. "xl sysrq <domain> <key>"
do the same sort of thing I think.


Otherwise I'm completely stumped. It's probably worth going back
to the
data sheet and making sure everything matches in the DTS, in
for virtulisation extension related things which might not be used by
native Linux (e,g, the vtimer interrupt SPI number etc), but really
that's getting a bit desperate.


     The guest doesn't respond to any of the sysrq key combinations, I
tried with both of the methods.

Which is expected because the console is not yet setup.

Based on the log you provided earlier, I would go start to check if the
guest receive the interrupt.

On the xen console (CTRL-a three times) you can type 'q' it will print
all the IRQ present in the LRs and which IRQ is pending for a given


     I've attached the full log from the domain dump below. But the
interesting part of the log is:

(XEN) Rangesets belonging to domain 1:
(XEN)     Interrupts { }
(XEN)     I/O Memory { }

     Perhaps I am interpreting this incorrectly, but it would seem that
no interrupts belong to domain 1?

These rangesets list the interrupt and I/O memory assigned to the guest (i.e passthrough).

In the case of the timer interrupt (physical and virtual), they are owned by Xen and Xen will emulated it for each guest.

From the logs the LRs are empty (see VCPU_LR) and no interrupts are currently pending.

I would add some printk in function gic_handle_irq in Linux (drivers/irqchip/irq-gic.c, assuming you are using GICv2) to see which IRQ is coming. FYI, the virt timer PPI is 27 and phys timer 30.


Julien Grall

Xen-users mailing list



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