search for: dmar

Hi, I''m not able to activate VT-d on my PC due to a buggy BIOS. Xen fails to parse ACPI DMAR table. There is a problem with 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_DR...

...ied all sorts of combinations of Xen versions and kernels to get this working. And, yes, VT and VT-d are enabled in my BIOS. 1) CentOS 5.2 SRPMS compiled with Xen 3.2.1. Adding pci=nommconf does not get it to boot. 2) Mercurial Xen-3.2-testing. Here, after adding pci=nommconf, I get: (XEN) [VT-D]dmar.c:441: RMRR is incorrect. (XEN) Failed to parse ACPI DMAR. Disabling VT-d. (XEN) [VT-D]ACPI DMAR:No DMAR devices found 3) Mercurial Xen-unstable, I get "I/O Virtualisation disabled" I can''t find any reason why this is the case. VT-D is not enabled. I would really like to find...

Hi, on a Nehalem system with VT-d enabled we are seeing strange ACPI-Table contents, especially a corrupted DMAR entry. The hypervisor shows following data on boot: (XEN) ACPI: RSDP 000F80E0, 0024 (r2 PTLTD ) (XEN) ACPI: XSDT BF7C469E, 00D4 (r1 PTLTD XSDT 60000 LTP 0) (XEN) ACPI: FACP BF7C9CC9, 00F4 (r3 FSC TYLERBRG 60000 PTL F4240) (XEN) ACPI: DSDT BF7C4772, 54D3 (r1 FSC D2619...

...e> <iommu model='intel'> <driver intremap='on' caching_mode='on' iotlb='on'/> </iommu> </devices> ... 2. guest has 'intel_iommu=on' enabled in kernel cmdline, then reboot guest 3. log in guest to check: # dmesg | grep -i DMAR [ 0.000000] ACPI: DMAR 000000007d83f000 00050 (v01 BOCHS BXPCDMAR 00000001 BXPC 00000001) [ 0.000000] DMAR: IOMMU enabled [ 0.155178] DMAR: Host address width 39 [ 0.155180] DMAR: DRHD base: 0x000000fed90000 flags: 0x1 [ 0.155221] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1200...

hi, I am trying the Xen unstable on X48 chipset these days but it failed due to an corrupted RMRR table in the ACPI. The following is the acpi dump of DMAR. DMAR @ 0x7fef1000 0000: 44 4d 41 52 20 01 00 00 01 d1 49 4e 54 45 4c 20 DMAR .....INTEL 0010: 44 58 34 38 42 54 32 20 12 06 00 00 4d 53 46 54 DX48BT2 ....MSFT 0020: 13 00 00 01 23 00 00 00 00 00 00 00 00 00 00 00 ....#........... 0030: 00 00 18 00 00 00 00 00 00 00 b0 fe 00 00 00 00 ....

...ouveau [ DRM] allocated 1920x1200 fb: 0x9000, bo ffff8808528bf800 [ 2.068437] fbcon: nouveaufb (fb0) is primary device [ 2.078765] nouveau [ DRM] 0xD1A1: Parsing digital output script table [ 2.139034] nouveau [ DRM] 0xD1F1: Parsing digital output script table [ 2.189610] dmar: DRHD: handling fault status reg 2 [ 2.189612] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 0 [ 2.189612] DMAR:[fault reason 06] PTE Read access is not set [ 2.190017] dmar: DRHD: handling fault status reg 102 [ 2.190019] dmar: DMAR:[DMA Read] Request device [01:00.0] fault...

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

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

Purchased DQ35JO on Vt-d/PCI passthrough wiki''s recommendations. Built latest xen-unstable and am getting the following via ''xm dmesg'': (XEN) [VT-D]dmar.c:374: RMRR error: base_addr d0000000 end_address cfffffff (XEN) Failed to parse ACPI DMAR. Disabling VT-d. My grub.conf looks like this: kernel /xen.gz vga=mode-0x0317 vtd=1 iommu=1 module /vmlinuz-2.6.18.8-xen ro root=/dev/XenVolGroup/LogVolXenDom0 rhgb quiet pcibac...

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 experiment, I delete the "return -EFAULT" and re-...

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 experiment, I delete the "return -EFAULT" and re-...

Hello List, I updated my server to CentOS 6.5. When i boot the system with the new kernel: 2.6.32-431.el6.x86_64 I get repeating the following message: dmar: DRHD: handling fault status reg 3 dmar: DMAR:[DMA Read] Request device [00:02.0] fault addr 1fc00000 DMAR:[fault reason 06] PTE Read access is not set I use a Intel Core i5-3550 CPU with vt-d enabled to use a DVB-S Card inside a Windows VM (kvm). With the old 6.4 Kernel all works (2.6.32-358.23...

...lo3-root_01 rd_NO_LUKS rd_LVM_LV=vg_onlo3/root_01 LANG=en_US.UTF-8 +rd_NO_MD SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=128M rhgb quiet rd_NO_DM rhgb +quiet kernel: 2.6.32-279.22.1.el6.i686 not-reportable: Your BIOS is broken reason: WARNING: at drivers/pci/dmar.c:594 warn_invalid_dmar+0x7f/0xa0() (Not tainted) time: Wed 20 Feb 2013 01:57:36 PM EST sosreport.tar.xz: Binary file, 460076 bytes backtrace: :WARNING: at drivers/pci/dmar.c:594 warn_invalid_dmar+0x7f/0xa0() (Not tainted) :Hardware name: HP Compaq dc7800 Small Form Factor :[Firmware...

lspci -vvv and -t attached Serial console output: http://pastebin.ca/2177395 Main error appears to be: (XEN) [VT-D]iommu.c:858: iommu_fault_status: Primary Pending Fault (XEN) [VT-D]iommu.c:833: DMAR:[DMA Read] Request device [00:1e.0] fault addr df8e5000, iommu reg = ffff82c3fff57000 (XEN) DMAR:[fault reason 06h] PTE Read access is not set onboard nic on the same bus is going down as depicted in the console log non-vtd passthrough to pv appears to work fine (shows up on domU lspci, di...

Rather than requiring the scopes to be the first members of their respective structures (so that casts can be used to switch between the different views), properly use types and container_of(). Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/passthrough/vtd/dmar.c +++ b/xen/drivers/passthrough/vtd/dmar.c @@ -304,13 +304,15 @@ static int __init scope_device_count(con static int __init acpi_parse_dev_scope( - const void *start, const void *end, void *acpi_entry, int type, u16 seg) + const void *start, const void *end, struct dmar_scope *scope, +...

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)

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)

During parsing DMAR table, if find RMRR is incorrect, return error. Signed-off-by: Weidong Han <weidong.han@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I''m using (XEN) Xen version 4.1.2 (Debian 4.1.2-2) (waldi at debian dot org) (gcc version 4.6.2 (Debian 4.6.2-6) ) Sat Dec 10 19:58:21 UTC 2011 With VT-d enabled in BIOS the ACPI Direct Memory Access remapping (DMAR) in the P6T Deluxe V2 (BIOS 1202, 2011/10/10) reports RMRR (Reserved Memory Region Reporting Structure) is bf7dc000 - bf7dbfff e820 table: 0000000000000000 - 000000000009e400 (usable) 000000000009e400 - 00000000000a0000 (reserved) 00000000000e4c00 - 0000000000100000 (...

...BB7FECFE, 0050 (r1 FUJ FJNB216 1080000 FUJ 100) (XEN) ACPI: SLIC BB7FED4E, 0176 (r1 FSC PC 1080000 FUJ 100) (XEN) ACPI: BOOT BB7FEEC4, 0028 (r1 FUJ FJNB216 1080000 FUJ 100) (XEN) ACPI: ASF! BB7EE000, 00A0 (r16 FUJ FJNB216 1080000 FUJ 100) (XEN) ACPI: DMAR BB7ED000, 00B8 (r1 INTEL CP_DALE 1 INTL 1) (XEN) ACPI: SSDT BB7DF000, 0A50 (r1 PmRef CpuPm 3000 INTL 20060912) (XEN) System RAM: 3606MB (3692780kB) (XEN) Domain heap initialised (XEN) Processor #0 6:5 APIC version 21 (XEN) Processor #4 6:5 APIC version 21 (XEN) Processor #1...