Displaying 12 results from an estimated 12 matches for "dmaru".
Did you mean:
dmar
2012 Nov 28
2
[PATCH] VT-d: make scope parsing code type safe
...nit )
return -ENOMEM;
@@ -463,7 +461,7 @@ acpi_parse_one_drhd(struct acpi_dmar_hea
dev_scope_start = (void *)(drhd + 1);
dev_scope_end = ((void *)drhd) + header->length;
ret = acpi_parse_dev_scope(dev_scope_start, dev_scope_end,
- dmaru, DMAR_TYPE, drhd->segment);
+ &dmaru->scope, DMAR_TYPE, drhd->segment);
if ( dmaru->include_all )
{
@@ -590,7 +588,7 @@ acpi_parse_one_rmrr(struct acpi_dmar_hea
dev_scope_start = (void *)(rmrr + 1);
dev_scope_end = ((void *)rmrr)...
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
2012 Apr 10
0
VT-d BIOS problem with DMAR/ACPI tables | Sabertooth X58
...h RMRR address range.
My configuration is :
- Debian Weezy
- Xen version 4.1.2 (Debian 4.1.2-2)
- Sabertooth X58 with last bios (1304)
- i7 - 960
I have the following message :
(XEN) [VT-D]dmar.c:704: Host address width 39
(XEN) [VT-D]dmar.c:719: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:413: dmaru->address = fbfff000
(XEN) [VT-D]iommu.c:1122: drhd->address = fbfff000 iommu->reg = ffff82c3fff57000
(XEN) [VT-D]iommu.c:1124: cap = c9008010e60262 ecap = f0207a
(XEN) [VT-D]dmar.c:341: endpoint: 0:1b.0
(XEN) [VT-D]dmar.c:719: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:413: dmaru->add...
2010 Sep 17
27
Problem: Pattern with vertical colored lines on the dom0 screen
...1 6:5 APIC version 21
(XEN) Processor #5 6:5 APIC version 21
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) [VT-D]dmar.c:679: Host address width 36
(XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:398: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:334: endpoint: 0:1b.0
(XEN) [VT-D]dmar.c: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...
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
2009 Mar 04
1
pv_ops kernel 2.6.29-rc6 boot failure
...by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
(XEN) [VT-D]dmar.c:460: Host address width 36
(XEN) [VT-D]dmar.c:469: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:337: dmaru->address = fedae000
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:469: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:337: dmaru->address = fedb0000
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:28...
2013 Jul 09
6
4.3 regression in booting on a particular platform
Jan,
I was given a machine to diagnose a boot problem on xen 4.3, that used
to work on 4.2, and have bisected to the following changeset:
commit d0d4635d034f202bb401a6efa3ba61530f3854ab
Author: Jan Beulich <jbeulich@suse.com>
Date: Thu Nov 22 10:47:58 2012 +0100
implement vmap()
... and use it as basis for a proper ioremap() on x86.
Signed-off-by: Jan Beulich
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)
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