Re: [Xen-devel] xen 4 only seeing one keyboard and mouse

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Tue, Aug 24, 2010 at 11:40:37PM +0100, M A Young wrote:
> On Tue, 24 Aug 2010, Konrad Rzeszutek Wilk wrote:
> 
> >Or is it done before Dom0 has been started? The c/s 20073 that
> >Keir graciously found does an extra step of programming the IOAPIC and
> >I wonder if doing that is sending the i8042 in some weird state.
> 
> The logs are attached.

Awesome, so
> (XEN)  NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
> (XEN)  00 000 00  1    0    0   0   0    0    0    00
> (XEN)  01 001 01  0    0    0   0   0    1    1    28
.. 
> (XEN)  0c 001 01  0    0    0   0   0    1    1    78
during boot they are set, then as Dom0 boots up it creates
its own copies of the IRQs and..
> xen: --> irq=2
..
> xen: --> irq=12
> (XEN) [2010-08-24 23:19:53] IOAPIC[0]: Set PCI routing entry (2-12 -> 0x78 -> 
> IRQ 12 Mode:0 Active:0)
> (XEN) [2010-08-24 23:19:53] IOAPIC[0]: Set PCI routing entry (2-1 -> 0x28 -> 
> IRQ 1 Mode:0 Active:0)

and the hypercall is done to get the vector number. OK good.
> (XEN) [2010-08-24 23:19:53] do_IRQ: 1.40 No irq handler for vector (irq -1)
> (XEN) [2010-08-24 23:19:54] do_IRQ: 1.120 No irq handler for vector (irq -1)
> (XEN) [2010-08-24 23:19:54] do_IRQ: 1.120 No irq handler for vector (irq -1)
> (XEN) [2010-08-24 23:19:54] do_IRQ: 1.120 No irq handler for vector (irq -1)

and then we expect the IRQ to work, but the hypervisor has no
recollection of us setting those IRQs.

So I think we need to ask Bastian for help - he made the changes in the
hypervisor so that IRQs below 16 could be programmed by the Dom0, and it
might be that we are missing some simple step of setting the
per_cpu[vector] field?

I am curious if you reverted c/s 21092 whether your machine would work
or not. If so, we need to talk to Bastian.

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


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