similar to: RE: VT-D RMRR is incorrect

reaver wrote: > > On Tue, Feb 24, 2009 at 12:36 AM, Dustin Henning > <Dustin.Henning@prd-inc.com> wrote: >> Christian, >>        I am not sure what lead me to believe you had an AMD system.  To >> summarize what I was trying to say, ASUS is claiming that this issue is >> unsupported because you use Linux, but at the end of the day, the issue >> has

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

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

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:

I'm looking at setting up a new machine to run CentOS 5 and a few VMWare machines to test Windows XP, Vista, and 7. I'm working with a custom PC shop and they've recommended I use either the ASUS PT6 or Intel DX58SO. Any feedback good or bad on either of these? Thanks! --Chris

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

Hi people. I had finally cross my USB to my DomU windows XP, justs 1 issue: USB 2.0 not working only 1.1 is working. I would to confirm with others that have the MoBo ASUS M4A89TD Pro/USB3 if u have been able to passthrough the USB ports to HVM windows? I had try different settings on my BIOS, different settings on Xen 4.1, this under Centos x64 AMD Athlon II 640. I receive the

testing, uname -ri 2.6.33-rc5-4-xen x86_64 rpm -qa | grep -i Xen-4 xen-4.0.0_20873_01-29.1.x86_64 cat test.cfg name = ''test'' builder = ''linux'' bootloader = ''/usr/lib/xen/boot/domUloader.py'' bootargs = ''--entry=xvda1:vmlinuz-xen,/boot/initrd-xen'' disk = [

Hi, I have an ASUS P6T Deluxe and I''m trying to use VT-d with Xen. I have also tried it with ESXi and Parallels Workstation Extreme - none of them work correctly. >From reading the xen-user and xen-devel list archives, I see that this motherboard has problems with malformed DMAR tables. Is there anything I can do to fix/workaround this or am I completely stuck? I did notice

Fix addr_to_dma_page() issue to return l1e correctly, and also clean up rmrr mapping code, make sure setup rmrr identify mapping just once per domain. This patch fixes the VT-d bug (Fail to boot smp Linux guest with VT-d NIC assigned on IA32e platform). Signed-off-by: Weidong Han <weidong.han@intel.com> _______________________________________________ Xen-devel mailing list

Platform : Nehalem, official Intel x58 with Core i7 920 (dx58so) Main (Console): Nvidia 9500 GT PCI Express Secondary: Nvidia 8800 GTS PCI Express Yes, I binned the ASUS P6T due to bad VT-d support in the BIOS. With the latest BIOS from Intel, the dx58so has enable/disable for VT-d, ICH FLR and Interrupt Mapping! Helped a lot with getting this working ... Dom0: 2.6.18-xen0 (built from

I have a chipset which supports VT-d (Intel X58) and, according to my motherboard manufacturers, VT-d is enabled in the BIOS and listed as "Intel VT." The problem is that xm dmesg shows "I/O virtualisation disabled" and I get this error message when I try to create a domU with a pci device assigned: ''Error: failed to assign device: maybe the platform doesn''t

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

This patch adds the function that reassign page-aligned memory resources, to dom0 linux. The function is useful when we assign I/O device to HVM domain using pci passthrough. When we assign a device to HVM domain using pci passthrough, the device needs to be assigned page-aligned memory resources. If the memory resource is not page-aligned, following error occurs. Error: pci: 0000:00:1d.7:

This patch adds "guestdev=" boot parameter. This boot parameter is used to reassign page-aligned memory resource and bind PCI back driver. Thanks, -- Yuji Shimada. Signed-off-by: Yuji Shimada <shimada-yxb@necst.nec.co.jp> diff -r 4769a6db78f5 -r fcefb8852878 Documentation/kernel-parameters.txt --- a/Documentation/kernel-parameters.txt Thu Dec 25 10:37:52 2008 +0900 +++

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

This patch maps RMRR in intel_iommu_add_device() if the device has RMRR; move domain_context_mapping() to be in front of list_move() in reassign_device_ownership(). Currently, hypervisor sets up devices and RMRR for dom0, and dom0 also adds devices for itself via hypercall. This is obviously duplicate. In order to allow old dom0 kernels to work with iommu-capable platforms, maybe it cannot be

Further to my messages back in May I have at last got round to trying to get my DomU to recognise USB devices. I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64. I have to manually make the port available before creating the DomU by issuing the command: xl pci-assignable-add 00:1a.0 otherwise nothing shows in: xl pci-assignable-list I have added this to my .cfg file as per the

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 ....#...........

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