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

Re: [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx



> -----Original Message-----
[snip]
> > (XEN) Domain heap initialised
> > (XEN) ACPI: 32/64X FACS address mismatch in FADT -
> > 8ce8ef80/0000000000000000, using 32
> > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
> > (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
> > (XEN) [VT-D]  RMRR address range 8d800000..8fffffff not in reserved
> > memory; need "iommu_inclusive_mapping=1"?

This is your problem. In versions prior to 4.11 (I think, and certainly 4.12) 
iommu_inclusive_mapping used to default on, whereas now it appears to default 
off. In most circumstances this is fine because there is a new flag, 
iommu_hwdom_reserved, which defaults on and this makes sure that all e820 
reserved regions are identity mapped (which usually covers undeclared RMRRs). 
You have the opposite problem... a declared RMRR which is not reserved, so you 
will need iommu_inclusive_mapping.

  Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

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