similar to: DQ35JO (Q35 chipset), Q6600, xen-unstable (~12/21), RMRR/DMAR error

Hi, i was trying to install CentOS 5.1 on new machine based on Intel Q35 desktop board, witch 2 SATA disks (configured as RAID 1) , 8GB RAM and Intel Core2 QUADCORE. The first problem was with install - it hangs before installer startup at ACPI messages. So i installed it with ACPI=off switch. The first problem is : Dec 7 09:54:01 vmhost1 kernel: BIOS bug, no explicit IRQ entries, using default

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 spent a few hours upgrading one of my Xen boxes so that I''d be able to use VT-d. I bought a DQ35JO because it seemed like a sure thing. I can successfully use pciback to hide and grab devices. Specifically I am trying to pass some USB controllers to Windows. The DQ35JO/ICH9DO appears to have two independent sets of USB UHCI/EHCI controllers: 00:1a.0 USB Controller: Intel

hi, This is what I get on the Intel DQ35JO. Is it critical? (XEN) Brought up 2 CPUs (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware

Hello all, I'm looking at buying an intel dq35jo mother board. From what I've read on the net other's have been using the board to one degree or another for a year now. My main concern is that I can install CentOS 5 over a network. Any comments? -- Milton Calnek BSc, A/Slt(Ret.) milton at calnek.com 306-717-8737 -- This message has been scanned for viruses and dangerous

im trying to do pcipassthrough to a hvm domain on xen 3.4.2 with jeremy''s pv_ops dom0 kernel 2.6.31.6 on debian lenny. dom0 kernel indicates that pciback cmdline options are unknown, but config shows CONFIG_XEN_PCIDEV_BACKEND=y is compiled in. is pciback broken on this kernel or something? all relevant information i can think is here, let me know if theres anything else you''d

I thought I''d pass along a few tips for getting the Intel DQ35JO motherboard to play nice with Xen: 1. The dom0 kernel won''t boot with CONFIG_PCI_MMCONFIG enabled. If you get a hang during boot after seeing this message: ACPI: PCI Root Bridge [PCI0] (0000:00) ...then MMCONFIG is your problem. Some kernels seem to support a pci=nommconfig option, but my Gentoo 2.6.21 Xen

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

I am happy to announce that I have successfully (and finally!) been able to pass a PCIe graphics card via VT-d to a Windows XP HVM DomU. About time! Config: -Intel Q6600 Core 2 Quad-Core, G0 stepping (I think) -Intel DQ35JO Motherboard, Q35 Chipset, BIOS v.991 (1/9/09), VT and VT-d enabled -nVidia 9500GT (for VT-d passthrough - DomU) -nVidia GeForce2 MX200 (Dom0 console) -Xen (build:

I am happy to announce that I have successfully (and finally!) been able to pass a PCIe graphics card via VT-d to a Windows XP HVM DomU. About time! Config: -Intel Q6600 Core 2 Quad-Core, G0 stepping (I think) -Intel DQ35JO Motherboard, Q35 Chipset, BIOS v.991 (1/9/09), VT and VT-d enabled -nVidia 9500GT (for VT-d passthrough - DomU) -nVidia GeForce2 MX200 (Dom0 console) -Xen (build:

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

Previously applied sanity check fixup is incorrect. Signed-off-by: Espen Skoglund <espen.skoglund@netronome.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

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

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:

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

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

On 03/11/2015 08:20 PM, Nerijus Baliunas wrote: > Laine Stump <laine@...> writes: > >> And it is also true that any machine with a SATA controller can't be >> migrated because of problems with the driver. I just talked to the >> person responsible for fixing these bugs in qemu, and he said that the >> patches will go upstream "soon", and that he

On 03/22/2015 08:23 PM, Nerijus Baliunas wrote: > On Thu, 12 Mar 2015 14:56:08 -0400 Laine Stump <laine@laine.org> wrote: > >> Here is the info straight from the author (I've also Cc'ed him to this >> mail): >> >> =============== >> The AHCI migration series is here: >> >>

On 03/23/2015 08:05 PM, Nerijus Baliunas wrote: > On Mon, 23 Mar 2015 10:36:33 -0400 John Snow <jsnow@redhat.com> wrote: > >>> Are the needed patches in 2.3.0-rc0? >>> Is it possible to backport AHCI migration to RHEL 7.1 qemu or will it be too much work? >> >> The patches that improve the stability of AHCI migration are in 2.3-rc0. >> We still have