similar to: [RFC][PATCH 6/6] HVM PCI Passthrough (non-IOMMU)

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,

I have a system whose cpu can run a hvm. I have some PCI devices that I would like to be able to pass through straight to the domU Specifically, I want to pass through a device to a Windows VM. No, I explicitly do _not_ have a system with Intel''s VT-d technology. In an ideal world, I would be able to pass the graphics and some arbitrary non-graphics PCI cards direct to the DomU.

Hi, I''m running a machine with: - Hypervisor: xen-unstable - Dom0: xen/next-2.6.32.17 commit c3f5aba942c7516a5c76c47345ff0a473daf2542 Hardware: -MSI 890FXA-GD70 with AMD IOMMU -Phenom X6 I''m trying to do PCI passthrough to a HVM, this fails with: Error: Failed to assign device to IOMMU (0000:04:00.0@100,msitranslate=1,power_mgmt=0) Error: pci: to avoid potential security

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

Hello, I''m trying to reverse-engineer a PCI sound card driver. The card is assigned to a Xen HVM guest (Windows) using PCI passthrough, the driver is installed and works. I had to compile Xen 4.2.3 from source as PCI passthrough is broken in 4.1.4-3+deb7u1 present in Debian Wheezy. Now I need to capture/log/dump/trace PIO and/or MMIO accesses that the driver does to the assigned

Hello, I saw some patches about PCI-passthrough for HVM(non-IOMMU) and I am interested in it. I want to assign my graphics card(nVidia GeForce 7900GS) to an HVM domain (Vista) in order to run 3D-intensive work(for example, 3D-games). What I want to ask is that is it really possible to pass the graphics card to HVM domain running Vista now? That is, have anyone ever successfully

Hello, I saw some patches about PCI-passthrough for HVM(non-IOMMU) and I am interested in it. I want to assign my graphics card(nVidia GeForce 7900GS) to an HVM domain (Vista) in order to run 3D-intensive work(for example, 3D-games). What I want to ask is that is it really possible to pass the graphics card to HVM domain running Vista now? That is, have anyone ever successfully

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

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) -

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,

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

Package: xen-hypervisor-4.1-amd64 Followup-For: Bug #706543 I beleive this was a regression caused by the XSA-36 security update. It was fixed upstream by 934a5253d932 "fix XSA-46 regression with xend/xm" http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=934a5253d932 this was also put into 4.1.x as 22d89f4a0960. Ian. -- System Information: Debian Release: jessie/sid APT prefers

Fixed : Double amount of memory from 128 to 256 and iommu works it out fine. RTFEM (read the fucking error message) : [ 0.872160] Kernel panic - not syncing: Out of memory and no killable processes... ________________________________________________________________________________________________________________ Frédéric Abel| RTS France BeNeLux | Quantum Corporation

Hi Xenners, I have tried to upgrade to kernel 3.5 and experienced the USB/PCI passthrough problem. This has not been "fixed" in 3.6 either. I do not know if this is qemu, xen or kernel related. I am using Xen 4.2 final and Xen 4.3-unstable to test. DomU is Windows 7 64 bit or Linux Fedora 17. In Windows, I get the little yellow triangle with Code 10 (I know this means nothing...

On 08/12/2015 02:34 PM, Alex Holst wrote: > I would really appreciate some pointers on what I am doing wrong here. > > I have a need to run multiple virtual guests which have each their own GPU and > some USB controllers passed-through. I am able to run one of the guests like > this (assuming vfio stuff has happened elsewhere), but I would prefer to use > virsh: > > kvm -M

This patch fixes libpci error handling. It can be applied to both ioemu-remote and ioemu. libpci returns ALL F when error occurs. Currently, if libpci returns ALL F, emulation stops. But it is possible that the field of real register which is read by guest software is ALL F. After applying this patch, if libpci returns ALL F, ioemu will log warning message and continue the emulation.

On Wed, 2013-06-05 at 16:53 -0500, Anthony Liguori wrote: > Existing PowerPC remaps PIO to MMAP so it works fine today. > > Future platforms may not do this but future platforms can use a > different device. They certainly won't be able to use the existing > drivers anyway. > > Ben, am I wrong here? Well, we do remap PIO, though it's ugly and annoying so we'd

On Wed, 2013-06-05 at 16:53 -0500, Anthony Liguori wrote: > Existing PowerPC remaps PIO to MMAP so it works fine today. > > Future platforms may not do this but future platforms can use a > different device. They certainly won't be able to use the existing > drivers anyway. > > Ben, am I wrong here? Well, we do remap PIO, though it's ugly and annoying so we'd

Quoting Laine Stump (laine@laine.org): > On 08/12/2015 02:34 PM, Alex Holst wrote: > > I would really appreciate some pointers on what I am doing wrong here. > > > > I have a need to run multiple virtual guests which have each their own GPU and > > some USB controllers passed-through. I am able to run one of the guests like > > this (assuming vfio stuff has