 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] VT-d warnings on Intel DQ35JO
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] VT-d warnings on Intel DQ35JO |
| From: | "Neo Jia" <neojia@xxxxxxxxx> |
| Date: | Thu, 5 Jun 2008 00:30:02 -0700 |
| Cc: | "Han, Weidong" <weidong.han@xxxxxxxxx> |
| Delivery-date: | Thu, 05 Jun 2008 00:30:25 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:mime-version:content-type:content-transfer-encoding :content-disposition; bh=nnUOgpWTZuKEwYeNbeMzJRbacCJ/RR+m+KgUOT4Tw4g=; b=dKZn2h817bsrrI/ngL+Et+ILaw3NAB4dGuaCYN6W8tX9qdMFR6btTyv9oheyBdjbBH rBCfJns9kBLumrs4eDHLHMpuHexamsmZPLQl+bCtF0FwXQNLnWrkrFgwxYmNeGbw6dCS uGwq1RAYOg9x8+XCxAjk7LQ8hd9hqgR+1kkp0= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type :content-transfer-encoding:content-disposition; b=ORLwGWmcyJWynqM4rDfAjVtPt75kKlWT92HEvEi2h9rTwuVsnJSPyNemiKPVF+o/gp qTAZ15C/rpqL3a7oZ3wibk5wt+FbM1bmxNeGvoinbPwebIHPJ2rwhlePCnZVj3DHf4Ud +c8gcRagDawr9EeRmbUZaCJT2MGSNVavu2NRM= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| 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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
hi, This is what I get on the Intel DQ35JO. Is it critical? (XEN) Brought up 2 CPUs (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found (XEN) I/O virtualisation enabled (XEN) I/O virtualisation for PV guests disabled (XEN) [VT-D]iommu.c:764: iommu_page_fault: iommu->reg = ffff828bfff57000 (XEN) [VT-D]iommu.c:733: iommu_fault_status: Fault Overflow (XEN) [VT-D]iommu.c:720: iommu_fault:DMA Write: 0:2.0 addr f00000000 REASON 5 iommu->reg = ffff828bfff57000 (XEN) print_vtd_entries: iommu = ffff83007aefb480 bdf = 0:2:0 gmfn = f00000 (XEN) root_entry = ffff83007c06e000 (XEN) root_entry[0] = 7c18b001 (XEN) context = ffff83007c18b000 (XEN) context[10] = 101_7d1dc001 (XEN) l3 = ffff83007d1dc000 (XEN) l3_index = 3c (XEN) l3[3c] = 0 (XEN) l3[3c] not present (XEN) *** LOADING DOMAIN 0 *** Thanks, Neo -- I would remember that if researchers were not ambitious probably today we haven't the technology we are using! _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] dom0 boot failure with 256G, Keir Fraser |
|---|---|
| Next by Date: | [Xen-devel] Re: dom0 boot failure with 256G, Keir Fraser |
| Previous by Thread: | [Xen-devel] Fwd: Xen src installation on Intel DQ35JO, Neo Jia |
| Next by Thread: | Re: [Xen-devel] VT-d warnings on Intel DQ35JO, Jean Guyader |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
