similar to: P6T RMRR clarification please

Greetings, I''m attempting to do gfx_passthru with the primary graphics adapter (03:00.0), passing it to a guest. I can unbind it from the host but when I fire up the guest OS my monitor loses signal from the graphics card and that''s that. The GFX card is dual DVI, I''ve tried both slots. Host is Linux 2.6.32.14-1.2.105.xendom0.fc12.x86_64, Guest is Windows 7. PC is an

Hi, I''ve successfully used VT-d on an ASUS P6T mainboard which is known to have really buggy RMRR tables. I tested passtrough with: - the onboard (fake-)raid-controller (no problems) - a pci card (no problems) - VGA cards (worked only partly - I''ll investigate that) I wrote a little patch to the code parsing the RMRR tables and enabled the following command line options:

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

Trying to set up PCI pass through with xen 3.2.1 on Debian Lenny, with xen Kernel 2.6.26... having no luck. I have the following configured... i) Virtualization and vt-d are both enabled in the bios, I have power cycled after making these changes. ii) I have these option in grub menu; iommu=1 pciback.permissive pciback.hide=(07:01.0)(01:00.0) vtd=1 iii) I have this in my cfg file

tmoore wrote: > > > I`ve raised a support case with ASUS to try to get them to fix the BIOS on > P6T Deluxe ... I`ll keep this thread updated. > > The IOMMU is seriously broken on this board, I have tried many workarounds > and it always results in failure. > > > Hello, did you get a reply? Somebody else has something new about the Asus P6T and this problem? How

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

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

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

Hi folks, currently I try to setup a new xen host v3.4.1 on top of a Asus P5E-VM DO (latest BIOS, Vt-d capable and enabled in BIOS) to migrate my extisting HVMs (Win2k3 server) running on Xen v3.3.0 to a new home. I want to switch over to 3.4.1 to (hopefully!) passthrough my ISDN board to a HVM domU. Unfortunate there seem some issue with the VT-d DMAR tables which is beyond my knowledge and

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

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

OK, cut two of the iommu reserved memory issue patch as we discussed... This patch adds a boolean boot parameter to xen to allow inclusive mapping of all memory below 4GB to the iommu mappings for dom0. The unusable ranges and memory occupied by xen are still excluded. The parameter is "iommu_inclusive_mapping=1" and is off by default. In addition to the parameter, a warning is also

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

Matching the comment in iommu_set_dom0_mapping(), map only actual RAM from the address range starting at 4G. It''s not clear though whether that comment is actually correct (which is why I''m sending this as RFC), but it is certain that on systems with sparse physical memory map we''re currently wasting a potentially significant amount of memory for setting up IOMMU page

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

Hi, Is there any configuration setting to increase the size of the ringbuffer used for Xen dmesg ? I wanted to check the advanced features supported on my Xen systems, on my Optiplex 755 I can read the info by running "xm dmesg" and searching for VMX: (XEN) VMX: Supported advanced features: (XEN) - APIC TPR shadow (XEN) - MSR direct-access bitmap But on my Supermicro system which

More information... I have pcifront showing as a module in the DomU and the usb shows in dmesg as: [ 3.167543] usbcore: registered new interface driver usbfs [ 3.167563] usbcore: registered new interface driver hub [ 3.167585] usbcore: registered new device driver usb [ 3.196056] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.196060] usb usb1: New USB device strings:

Hi. Package: xen-hypervisor-4.1-amd64 Starting guest VM, after package upgrade: xm create winxp Using config file "./winxp". Error: failed to assign device: maybe the platform doesn't support VT-d, or VT-d isn't enabled properly? If I set up VM properly after few months, but I remember, I met same error only after package upgrade. Pastebin logs, for check my errors: xm info