similar to: PCI passthrough to a HVM *without* VT-d ?

int.patch: - Supports only level-triggered interrupts. Edge interrupts support will be added shortly (should be fairly simple) - Change polarity trick: in order to reflect the external device''s assertion state, the ioapic pin gets its polarity changed whenever an interrupt occur. So an interrupt is generated when the _external_ line is asserted (then,

Hi, I really need help. I spent 2 days already on this pci passthrough thing. I''m using Xen 3.2.1 with Centos 5.2 64 bits on intel VT. I''d like to use PCI passthrough and I don''t think I need VT-D functionality. I''m trying to pass PCI 12:01.0 to my domU guest. I got this error when I use "xm create /etc/xen/hvm_centos_2.cfg" Using config file

Hello, I am looking into building a workstation using Xen to host several operating systems. Looking at the pci passthrough requirements of Xen4.1 on the VTdHowTo<http://wiki.xensource.com/xenwiki/VTdHowTo>page, I am a little puzzled with the fact that only Intel Core2Duo (with VT-x), Core2Quad, i7 and Core i5 (vPro Brand) CPU''s are supported while motherboards with the i55x0

Hi all, I recently upgraded my Xen 3.2.1 to 3.3.1 on Centos 5.2. Everything seems to have gone pretty smoothly except I have a few issues. My system specs are: 4GB RAM Q6600 quad core Intel CPU P5E-VM DO Q35 Intel mobo (VT-d enabled) Skystar2 DVB PCI card passed through to HVM DomU HVM Windows XP SP3 DomU 1. When I restart my DomU, it shuts down and turns into Domain-Unnamed but

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

Is pci passthrough enabled for VT enabled hosts? Searching through the mailing list, it appears that as of March, pci passthrough only worked on paravirtualized hosts, not unmodified hosts. Has this situation changed? Thanks --Nathan White _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi everyone, after following in the footsteps of the following discussion (http://lists.xenproject.org/archives/html/xen-users/2013-09/msg00106.html) I had been able to turn my GTX 480 into a Quadro 6000. When I VT-d passthrough it to a Debian jessie VM it shows up fine and CUDA 5.5 seems to function properly up to a point: lspci -v: 00:04.0 VGA compatible controller: NVIDIA Corporation GF100GL

Hi all! I''m hoping someone here might be able to help. I''m familiar with several UNIX''es, though farily new to Linux... I''m running RHEL 5.2. I''ve got the RHEL kernel headers installed, etc, and compiled xen-3.3. Once that was built, I rebuilt libvirt, etc, the kernel, and all the modules. The whole mess boots and runs fine... mostly. My hardware

I am trying to get hotplugable USB support in a Windows HVM using Xen 3.2 on Fedora 8. I am running a Dell 755 workstation with VT-D support and I am attempting to use the PCI passthrough process to grab a USB controller from the workstation and make it available to the Windows XP DomU. I have successfully hidden the USB controller from Dom0 and my Windows XP VM does detect a "New USB

The following 5 patches are re-submissions of the vt-d patch. This set of patches has been tested against cs# 15080 and is now much more mature and tested against more environments than the original patch. Specifically, we have successfully tested the patch with following environements: - 32/64-bit Linux HVM guest - 32-bit Windows XP/Vista (64-bit should work but did not test) -

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

Hi, guys. I''ve been trying to use the pci-phantom command line options to xen so as to work around the hardware issue with the Marvell 88SE91xx SATA controllers in IOMMU ([Intel:] VT-d) mode, but I cannot seem to get my head around it. From having had a glance here: http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html and in particular the syntax described as such:

Hi all, Thought I''d share my success with VT-d. I picked up an Asus P5E-VM DO motherboard as it was relatively cheap and had an extra PCI slot compared to the Intel Q35 board. The people on #xen IRC were very helpful. I wasted 2 days trying to get things working on Ubuntu and OpenSUSE with forward patched versions of Xen for newer kernels. Ended up using CentOS 5.1 which has the requred

diff -r e6266fc76d08 -r 6feac926cf80 xen/drivers/passthrough/vtd/iommu.c --- a/xen/drivers/passthrough/vtd/iommu.c Fri Jul 27 12:22:13 2012 +0200 +++ b/xen/drivers/passthrough/vtd/iommu.c Mon Jul 30 15:35:16 2012 -0700 @@ -2137,6 +2137,15 @@ int __init intel_vtd_setup(void) { iommu = drhd->iommu; + printk("Intel VT-d supported page sizes: 4kB"); + if

According to vt-d specs, the addr in IOTLB invalidation descriptor should be 4K page aligned. Signed-off-by: Yang Zhang <yang.z.zhang@Intel.com> diff -r 0455d8317631 xen/drivers/passthrough/vtd/qinval.c --- a/xen/drivers/passthrough/vtd/qinval.c Thu Jun 28 18:43:28 2012 +0100 +++ b/xen/drivers/passthrough/vtd/qinval.c Wed Jul 11 08:43:24 2012 +0800 @@ -140,7 +140,7 @@ static int

Implement pci passthrough for HVM guests for NetBSD Dom0. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> From: Manuel Bouyer <bouyer@netbsd.org> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85689 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen

Hi, I am using opensuse as my dome and I tried to make a NIC card work in PCI passthrough. pciback is installed as a module in this kernel. I unbound all the NIC''s from dom0 driver and bound them to PCI back. I then modified the domU config file to include the pci device. When the system started booting up, I NICs were recognized however they failed to attach. This is the message I got,

... instead of open coding it. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/passthrough/vtd/iommu.c +++ b/xen/drivers/passthrough/vtd/iommu.c @@ -1079,22 +1079,11 @@ static void dma_msi_set_affinity(struct return; } - memset(&msg, 0, sizeof(msg)); - msg.data = MSI_DATA_VECTOR(desc->arch.vector) & 0xff; - msg.data |= 1 << 14; -

libpci.patch: - A library to access the PCI config space, probe the bus for devices, etc. It is basically a copy & paste from the libpci app. - Uses the 0xcf8/0xcfc method to read the config. - PIO/MMIO low-level access functions. Signed-off-by: Alex Novik <alex@neocleus.com> _______________________________________________ Xen-devel mailing list

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