[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen supported LAPIC features
On 08/10/13 20:37, Hoyer, David wrote: > Output from xl dmesg: Note that I have modified Xen to partition off some > of my DRAM as RAID CACHE in my E820 tables due to a specific need that we > have. This is under early development by us. > > > (XEN) Freed 264kB init memory. > (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from > 0x000000002504005b to 0x0000000025040059. > (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from > 0x000000002504005b to 0x0000000025040059. > (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from > 0x000000002504005b to 0x0000000025040059. > (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from > 0x000000002504005b to 0x0000000025040059. > (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from > 0x000000002504005b to 0x0000000025040059. > (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from > 0x000000002504005b to 0x0000000025040059. > (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from > 0x000000002504005b to 0x0000000025040059. > (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from > 0x000000002504005b to 0x0000000025040059. > (XEN) domctl.c:1581: E820 RAID CACHE from Domain-1 > (XEN) domctl.c:1597: E820 RAID CACHE Addr=0x0000000300000000 > Size=0x0000000080000000 > (XEN) physdev.c:178: dom1: 17:-1 already mapped to 17 > (XEN) physdev.c:178: dom1: 31:-1 already mapped to 21 > (XEN) physdev.c:178: dom1: 39:-1 already mapped to 22 > (XEN) physdev.c:178: dom1: 31:-1 already mapped to 21 > (XEN) physdev.c:178: dom1: 39:-1 already mapped to 22 > (XEN) physdev.c:178: dom1: 31:-1 already mapped to 21 > (XEN) physdev.c:178: dom1: 39:-1 already mapped to 22 > (XEN) vioapic.c:197:d1 vioapic_write_indirect error register 3 Without seeing the changes you have made for the raid cache, I cant tell whether you have broken something in Xen. However, this final error message from vioapic.c proves that you have a buggy IOAPIC driver dom1 (which I presume is your domU); It is attempting to read IOAPIC register 0x3 which doesn't exist in real hardware (or certainly not in any spec I have encountered). The errors from physdev.c are from physdev_map_pirq(). Given the number of PCI devices you are trying to pass through, you might have run out of pirqs for domU, although I would expect a rather more direct error message. Try booting xen with "extra_guest_irqs=64" or so. The default is for a limit of 32. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |