search for: acpi_dmar_rmrr

Displaying 10 results from an estimated 10 matches for "acpi_dmar_rmrr".

2010 May 12
44
Xen4 / Intel DX58SO Mobo / VT-d not working
Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as
2010 May 12
44
Xen4 / Intel DX58SO Mobo / VT-d not working
Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as
2012 Apr 10
0
VT-d BIOS problem with DMAR/ACPI tables | Sabertooth X58
...[VT-D]iommu.c:1122: drhd->address = fbffe000 iommu->reg = ffff82c3fff56000 (XEN) [VT-D]iommu.c:1124: cap = c90780106f0462 ecap = f020fe (XEN) [VT-D]dmar.c:356:   IOAPIC: f0:1f.7 (XEN) [VT-D]dmar.c:356:   IOAPIC: 0:13.0 (XEN) [VT-D]dmar.c:427:   flags: INCLUDE_ALL (XEN) [VT-D]dmar.c:724: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:341:   endpoint: 0:1d.0 (XEN) [VT-D]dmar.c:341:   endpoint: 0:1d.1 (XEN) [VT-D]dmar.c:341:   endpoint: 0:1d.2 (XEN) [VT-D]dmar.c:341:   endpoint: 0:1d.7 (XEN) [VT-D]dmar.c:341:   endpoint: 0:1a.0 (XEN) [VT-D]dmar.c:341:   endpoint: 0:1a.1 (XEN) [VT-D]dmar.c:341:   endpoint: 0:1a...
2010 Nov 29
13
VTD not working on Intel DX58SO w/ Xen 4.0.1
Hello, I''m having problems with VTD on this board. The board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU (0000:05:00.0@100,msitranslate=1,power_mgmt=0)
2010 Nov 29
13
VTD not working on Intel DX58SO w/ Xen 4.0.1
Hello, I''m having problems with VTD on this board. The board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU (0000:05:00.0@100,msitranslate=1,power_mgmt=0)
2008 Aug 05
18
RE: Xen-3.2.1 VT-d Support (NOT SURE WHETHER IT''S A BUG OR...)
Hello, I''m also seeing this exact same problem. I''ve posted on xen-users, but did not get an answer. Venkat seems to be experiencing the same problem as me. I have the latest BIOS for my motherboard DQ35JO. (BIOS ver 933) I''m running a Q6600 as well. It hangs at "Brought up 4 CPUs." I''ve tried all sorts of combinations of Xen versions and kernels to
2009 Feb 13
12
VT-D RMRR is incorrect
I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit) on a SUPERMICRO C7X58 board I see the following the error in my boot log. (XEN) [VT-D]dmar.c:372: RMRR is incorrect. This problem is caused by this condition in dmr.c:372. if ( rmrr->base_address >= rmrr->end_address ) { dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n"); return -EFAULT; } As an
2009 Feb 13
12
VT-D RMRR is incorrect
I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit) on a SUPERMICRO C7X58 board I see the following the error in my boot log. (XEN) [VT-D]dmar.c:372: RMRR is incorrect. This problem is caused by this condition in dmr.c:372. if ( rmrr->base_address >= rmrr->end_address ) { dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n"); return -EFAULT; } As an
2010 Sep 17
27
Problem: Pattern with vertical colored lines on the dom0 screen
...694: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:398: dmaru->address = fed91000 (XEN) [VT-D]dmar.c:334: endpoint: 0:2.0 (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:398: dmaru->address = fed93000 (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 (XEN) [VT-D]dmar.c:334: endpoint: 0:1a.0 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr bb6e9000 end_address bb6fffff (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:2.0 (XEN) [VT-D]dmar.c:571: RMRR region: base_a...
2009 Mar 04
1
pv_ops kernel 2.6.29-rc6 boot failure
...und endpoint: bdf = 0:3.0 (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:3.2 (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:3.3 (XEN) [VT-D]dmar.c:469: found ACPI_DMAR_DRHD (XEN) [VT-D]dmar.c:337: dmaru->address = fedb1000 (XEN) [VT-D]dmar.c:346: found INCLUDE_ALL (XEN) [VT-D]dmar.c:473: found ACPI_DMAR_RMRR (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1d.0 (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1d.1 (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1d.2 (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1d.7 (XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1a.0 (XEN) [VT-D]dmar.c:288: found endp...