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

["Han, Weidong" <weidong.han@xxxxxxxxx>]

'vtd=1' is old parameter to enable VT-d. It's replaced by 'iommu' parameter for 
a long time. The 'iommu=' parameter values are as follows:

 *   off|no|false|disable   Disable IOMMU (default)
 *   pv                                 Enable IOMMU for PV domains
 *   no-pv                      Disable IOMMU for PV domains (default)
 *   force|required             Don't boot unless IOMMU is enabled
 *   passthrough                Enable VT-d DMA passthrough (no DMA translation 
for Dom0)
 *   no-snoop                   Disable VT-d Snoop Control
 *   no-qinval                  Disable VT-d Queued Invalidation
 *   no-intremap             Disable VT-d Interrupt Remapping

Usually, you just need 'iommu=1' to enable IOMMU. When IOMMU is enabled, most 
of VT-d features (snoop control, queued invalidation and interrupt remapping) 
are enabled by default if they are available. 

When RMRR address range is not in reserved memory (BIOS issue), can use 
'iommu_inclusive_mapping=1' to work around it.

Regards,
Weidong

Bonenkamp, Ralf wrote:
> Dear Teo,
> 
> I tried all combinations
> - kernel /xen.gz iommu=1
> - kernel /xen.gz iommu_inclusive_mapping=1
> - kernel /xen.gz iommu=1 iommu_inclusive_mapping=1
> 
> And got the same result at xm dmesg on my mobo ;-)
> 
> I noticed that there is another switch mentioned named 'vtd=1' in
> some postings. The wiki at http://wiki.xensource.com/xenwiki/VTdHowTo
> does not mention any of those switches. Hopefully I can spare time in
> the next days to sort this switches out and prepare some sort of
> beginners guide to this topic...    
> 
> Regards,
> Ralf
> 
> 
> -----Original Message-----
> From: Teo En Ming (Zhang Enming) [mailto:enming.teo@xxxxxxxxxxxxxxx]
> Sent: Mittwoch, 19. August 2009 04:44
> To: pasik@xxxxxx; Bonenkamp, Ralf
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-devel] Vt-d not working with 3.4.1
> 
> Hi,
> 
> Is it not sufficient to parse iommu=1 only?
> 
> kernel /xen.gz iommu=1
> 
> We should also add iommu_inclusive_mapping=1?
> 
> So it becomes
> 
> kernel /xen.gz iommu=1 iommu_inclusive_mapping=1
> 
> Regards,
> 
> Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)
> BEng(Hons)(Mechanical Engineering)
> Technical Support Engineer
> Information Technology Department
> Asiasoft Online Pte Ltd
> Tampines Central 1 #04-01 Tampines Plaza
> Singapore 529541
> Republic of Singapore
> Mobile: +65-9648-9798
> MSN: teoenming@xxxxxxxxxxx
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Pasi
> Kärkkäinen 
> Sent: Monday, August 17, 2009 10:32 PM
> 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
> 
> Internal Virus Database is out of date.
> Checked by AVG - www.avg.com
> Version: 8.5.392 / Virus Database: 270.13.49/2295 - Release Date:
> 08/10/09 18:19:00
> 
> Internal Virus Database is out of date.
> Checked by AVG - www.avg.com
> Version: 8.5.392 / Virus Database: 270.13.49/2295 - Release Date:
> 08/10/09 18:19:00
> 
> 
> 
> _______________________________________________
> 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