similar to: wheezy VT-d passthrough test: DMAR:[fault reason 06h] PTE Read access is not set

Displaying 20 results from an estimated 3000 matches similar to: "wheezy VT-d passthrough test: DMAR:[fault reason 06h] PTE Read access is not set"

2012 Apr 10
0
VT-d BIOS problem with DMAR/ACPI tables | Sabertooth X58
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
2009 Aug 10
0
Vt-d not working with 3.4.1
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
2010 Oct 28
0
HVM + IGD Graphics + 4GB RAM = Soft Lockup
I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()
2010 Oct 28
0
HVM + IGD Graphics + 4GB RAM = Soft Lockup
I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()
2013 Dec 07
0
DMAR Problem since 6.5
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
2008 Apr 10
0
[PATCH] VT-d: DMAR device scope parse fixup
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
2011 May 19
5
vcpu-pin cause dom0 kernel panic
I use xen 4.0(dom0 is suse11.sp1,2.6.32 x86_64) on Dell R710 with PERC H700 RAID adapter. --Intel(R) Xeon(R) CPU E5620 @ 2.40GHz --8 CPU cores. --Memory 64G --RAID5 4.5T When I dedicated (pin) a CPU core only for dom0 use. (I specify "dom0_max_vcpus=1 dom0_vcpus_pin" options for Xen) I got dom0 kernel panic error(pin-1-5.30.bmp) When I pin 2 core to dom0, the dom0 system can boot up,
2008 Dec 23
1
DQ35JO (Q35 chipset), Q6600, xen-unstable (~12/21), RMRR/DMAR error
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
2008 Oct 25
2
VTd - PCI Passthrough - VMError: fail to assign device
Dear Users, Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64: After i want to start the HVM i get: VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn''t exist. [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=5 [2008-10-25 19:59:30 2460] DEBUG (__init__:1072)
2008 Jul 23
0
[PATCH] [VTD] Add RMRR check in DMAR parsing
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
2008 Jun 05
1
VT-d warnings on Intel DQ35JO
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
2010 Sep 17
27
Problem: Pattern with vertical colored lines on the dom0 screen
Hi list, I have a problem with a new laptop (reproducable on other machines too) and the xen hypervisor. When the hypervisor gets booted with VESA mode 800x600 I see some messages and then the screen contents is switched into a pattern of vertical colored lines and never comes back. In text mode all works well, but later the pattern appears when the X servers starts. I disabled VTd in the bios
2013 Nov 12
0
InfiniBand Passthrough not working
2012 Nov 28
2
[PATCH] VT-d: make scope parsing code type safe
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
2009 Jan 23
0
ASUS p6t, i7 920, vt-d broken.....
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
2014 Jan 19
2
PCI Passthrough
I'm trying to pass-through my VGA card to a guest session. I found: http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM - which is very frustrating because there's no date on the documentation. I suspect it's old. It does clearly say that you must have VT-d support for pci pass-through. It then goes on to say "Some work towards allowing this ["software
2010 Oct 08
1
VT-d with P6T Deluxe
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
2012 Nov 27
2
Intel VT-d and Asus Desktop/Workstation mainboards, eg. Asus P9X79 WS
Good day to you Im a casual Xen user and am also using I/O Virtualization. I had always trouble getting DMAR tables (and IOMMU) recognized with Asus Mainboards, despite the fact that I always used this boards a lot. Since the Nehalem Intel architecture, I looked into Intel Mainboards due the fact that this seems to work out with Xen, Linux and VT-d. My request is, that someone who tried Asus
2010 Apr 13
1
Xen breaks aacraid
Hello, I''m using Xen 4.0.0 compiled from source with the 2.6.31.13 kernel that it pulls down on its own. I added support for the aacraid driver to the kernel using ''make menuconfig'' from the build-linux-2.6-pvops_x86_64 subdirectory, and then built and installed the whole thing using ''make install'' from the xen-4.0.0 directory. I compiled this
2013 May 01
6
Bug#706543: xen-hypervisor-4.1-amd64: HVM PCI Passthrough not working any more after last upgrade
Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3 Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash