I have more information. If I boot giving xen the nosmp option then it can
see the laptop's keyboard. If I compare the xm demesg output of boots with
and without nosmp (having also run xm debug-keys z) I get the output
below. On reflection I think the do_IRQ warnings migth be relevant. The
full logs are attached.
Michale Young
9c9
< (XEN) Command line:
---
(XEN) Command line: nosmp
48c48
< (XEN) Detected 2394.072 MHz processor.
---
(XEN) Detected 2394.108 MHz processor.
58d57
< (XEN) Total of 2 processors activated.
61d59
< (XEN) checking TSC synchronization across 2 CPUs: passed.
63c61
< (XEN) Brought up 2 CPUs
---
(XEN) Brought up 1 CPUs
68c66
< (XEN) Dom0 alloc.: 0000000110000000->0000000118000000 (967236 pages to be
allocated)
---
(XEN) Dom0 alloc.: 0000000110000000->0000000118000000 (967255 pages to be
allocated)
72c70
< (XEN) Phys-Mach map: ffffffff83b38000->ffffffff842d9220
---
(XEN) Phys-Mach map: ffffffff83b38000->ffffffff842d92b8
78c76
< (XEN) Dom0 has maximum 2 VCPUs
---
(XEN) Dom0 has maximum 1 VCPUs
86,95d83
< (XEN) do_IRQ: 1.120 No irq handler for vector (irq -1)
< (XEN) do_IRQ: 1.144 No irq handler for vector (irq -1)
< (XEN) do_IRQ: 1.144 No irq handler for vector (irq -1)
< (XEN) do_IRQ: 1.144 No irq handler for vector (irq -1)
< (XEN) do_IRQ: 1.144 No irq handler for vector (irq -1)
< (XEN) do_IRQ: 1.144 No irq handler for vector (irq -1)
< (XEN) do_IRQ: 1.144 No irq handler for vector (irq -1)
< (XEN) do_IRQ: 1.144 No irq handler for vector (irq -1)
< (XEN) do_IRQ: 1.144 No irq handler for vector (irq -1)
< (XEN) do_IRQ: 1.144 No irq handler for vector (irq -1)
123c111
< (XEN) 0d 003 03 1 0 0 0 0 1 1 88
---
(XEN) 0d 001 01 1 0 0 0 0 1 1 88
127c115
< (XEN) 11 003 03 1 1 0 1 0 1 1 A8
---
(XEN) 11 001 01 1 1 0 1 0 1 1 A8
xm.dmesg.vanilla
Description: Text document
xm.dmesg.nosmp
Description: Text document
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
| 
Home