[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] 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
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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |