WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

On Mon, Aug 17, 2009 at 04:46:29PM +0200, Bonenkamp, Ralf wrote:
> 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...
> 

Ok. I remember discussions about Asus having buggy BIOS for VT-d stuff, so
maybe that's your problem here aswell..

I can't unfortunately help you more.. hopefully others can.

-- Pasi

> 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