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] trying to get vt-d working with xen 4.0.0 stable + 2.6.3

To: c4pt4inkrunch@xxxxxxxxx
Subject: Re: [Xen-devel] trying to get vt-d working with xen 4.0.0 stable + 2.6.32.10 pvops kernel with .config file from the
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 4 May 2010 10:49:10 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 04 May 2010 08:11:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <0016e64765d2184ed30485011daf@xxxxxxxxxx>
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: <0016e64765d2184ed30485011daf@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Sat, Apr 24, 2010 at 08:08:56PM +0000, c4pt4inkrunch@xxxxxxxxx wrote:
> here is my xm dmesg i was wondering if anyone knew about these DMAR  

.. snip..
> (XEN) [VT-D]iommu.c:1078: drhd->address = fe71a000 iommu->reg = fff17000
> (XEN) [VT-D]iommu.c:1080: cap = ffffffffffffffff ecap = ffffffffffffffff
> (XEN) [VT-D]iommu.c:1086: IOMMU: unsupported

Line 1086.

1083     if ( cap_fault_reg_offset(iommu->cap) +
1084          cap_num_fault_regs(iommu->cap) * PRIMARY_FAULT_REG_LEN >=
PAGE_SIZE ||
1085          ecap_iotlb_offset(iommu->ecap) >= PAGE_SIZE )
1086     {


The iommu->cap and iommu->ecap are used. And as you can see below
the values are all 0xfffffffffffffffff which are pretty bogus.

> (XEN) ---- print_iommu_regs ----
> (XEN) drhd->address = fe71a000
> (XEN) VER = ffffffff
> (XEN) CAP = ffffffffffffffff
> (XEN) n_fault_reg = 100
> (XEN) fault_recording_offset = 3ff0
> (XEN) ECAP = ffffffffffffffff
> (XEN) GCMD = ffffffff
> (XEN) GSTS = ffffffff
> (XEN) RTADDR = ffffffffffffffff
> (XEN) CCMD = ffffffffffffffff
> (XEN) FSTS = ffffffff
> (XEN) FECTL = ffffffff
> (XEN) FEDATA = ffffffff
> (XEN) FEADDR = ffffffff
> (XEN) FEUADDR = ffffffff
> (XEN) I/O virtualisation disabled
> (XEN) Total of 8 processors activated.

Looks to me that your hardware isn't working right.

So to fix this, please follow this link:

"Intel developers also want to know about broken IOMMU/VT-d BIOS
implementations, see this email:
+http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00841.html,
so let them know all the details about your hardware and
+software if you have broken BIOS. "


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>