>>> On 16.05.14 at 16:48, <ross.philip...@citrix.com> wrote: > On 05/16/2014 06:08 AM, Jan Beulich wrote: >>>>> On 16.05.14 at 10:58, <i...@hellion.org.uk> wrote: >>> So it seems like dom0 is unable to (correctly) bind to some hardware >>> interrupts. I wonder if these messages from Xen's dmesg are relevant. >>> (XEN) Not enabling x2APIC: depends on iommu_supports_eim. >>> (XEN) I/O virtualisation disabled >>> (XEN) Enabled directed EOI with ioapic_ack_old on! >> >> The last one certainly isn't, and the first two shouldn't (albeit the >> non-Xen kernel is running in x2APIC mode). That difference is likely >> because the Xen and non-Xen boots are with differing BIOS >> configurations, or on different machines: The non-Xen boot shows >> a DMAR ACPI table, while the Xen one doesn't. > > Doesn't Xen hide the DMAR from dom0 on purpose? I think it renames it to > XMAR IIRC.
Sure. It's XMAR in the kernel-on-Xen log, but there's no DMAR in the Xen one. Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
