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@lists.xensource.com http://lists.xensource.com/xen-devel
Neo Jia wrote:> 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 *** >I had almost the same error with this same motherboard, you should upgrade your bios. -- Jean Guyader _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Apparently Analagous Threads
- VTd - PCI Passthrough - VMError: fail to assign device
- [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000
- DQ35JO (Q35 chipset), Q6600, xen-unstable (~12/21), RMRR/DMAR error
- Xen 3.2.1, Intel DQ35JO, VT-d not working with Windows 2003
- CentOS 5.1 on intel DQ35JO , Q35 chipsed based board