This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] Vt-d not working with 3.4.1

To: 'Ross Philipson' <Ross.Philipson@xxxxxxxxxx>, "'Bonenkamp, Ralf'" <ralf.bonenkamp@xxxxxxxx>, "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Vt-d not working with 3.4.1
From: "Han, Weidong" <weidong.han@xxxxxxxxx>
Date: Tue, 18 Aug 2009 13:43:00 +0800
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Mon, 17 Aug 2009 22:45:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <831D55AF5A11D64C9B4B43F59EEBF72035FE85F76D@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <F528B4FC44C6E048B04DB369486AA8D101E2B55E@xxxxxxxxxxxxxx> <20090817143154.GZ24960@xxxxxxxxxxxxxxx> <F528B4FC44C6E048B04DB369486AA8D101E2B85E@xxxxxxxxxxxxxx> <831D55AF5A11D64C9B4B43F59EEBF72035FE85F76D@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcofR4EoYS8zkwTASQCZ9KCaATWC1gAAR9IAAAB9SuAAHsI14A==
Thread-topic: [Xen-devel] Vt-d not working with 3.4.1
Yes, we usually observed that the iommu fault on bdf 00:02.0 is harmless. What 
problem of VT-d did you find? Dom0 hang? Cannot passthrough device?


Ross Philipson wrote:
> The message will remain regardless of whether you set
> iommu_inclusive_mapping or not. The parameter is there to work around
> the underlying issue but the issue is not actually corrected. So the
> code that generates the message (which is detecting discrepancies
> between the e820 map and the DMAR RMRR values) will continue to
> report this even though you used the parameter. The real question is
> whether you are experiencing some other problems beyond the warning
> message - like a boot hang?       
> Thanks
> Ross
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Bonenkamp, Ralf  
> Sent: Monday, August 17, 2009 10:46 AM
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-devel] Vt-d not working with 3.4.1
> Hi Pasi,
> Sorry - I forgot to mention that I've tried setting the
> iommu_inclusive_mapping=1 parameter too, but unfortunate I posted the
> output from a previous attempt without this parameter.  
> The xm dmesg output and the DMAR parsing error remains the same. This
> was the reason posting, because I ran out of ideas... 
> Best regards
> Ralf Bonenkamp
> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@xxxxxx]
> Sent: Montag, 17. August 2009 16:32
> To: Bonenkamp, Ralf
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Vt-d not working with 3.4.1
> On Sat, Aug 08, 2009 at 11:53:23PM +0200, Bonenkamp, Ralf wrote:
>> Hi folks,
>> currently I try to setup a new xen host v3.4.1 on top of a Asus
>> P5E-VM DO (latest BIOS, Vt-d capable and enabled in BIOS) to migrate
>> my extisting HVMs (Win2k3 server) running on Xen v3.3.0 to a new
>> home. I want to switch over to 3.4.1 to (hopefully!) passthrough my
>> ISDN board to a HVM domU. Unfortunate there seem some issue with the
>> VT-d DMAR tables which is beyond my knowledge and probably someone
>> has some hint how to proceed? :-) 
> Well did you try iommu_inclusive_mapping=1, like it suggests ?
>> (XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory
>> base = 7d600000 end = 7dffffff; iommu_inclusive_mapping=1 parameter
>> may be needed. (XEN) Intel VT-d DMAR tables have been parsed.
> -- Pasi
> _______________________________________________
> 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

Xen-devel mailing list