similar to: pci passthrough on unstable

Hi, When setting up my Xen box, I needed PCI passthrough (for a pair of DVB cards). This works very well for mid-august testing Xen, but im having networking problems. I understand that the PCI passthrough code was broken in Unstable at that date - is this still the case? any workarounds? thanks g _______________________________________________ Xen-users mailing list

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

Hi all, I''ve been trying to understand the pci_setup function in hvmloader.c in Xen unstable. I''m kinda lost at Line 328. base = (resource->base + bar_sz - 1) & ~(bar_sz - 1) I''d appreciate if someone could explain to me why base is calculated this way. Specifically, I don''t understand the bitwise AND with the one''s complements of

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)

I hope someone can enlighten me. I have a quad-port Intel 82580 nic (igb driver) on my system and I''d like to dedicate each nic to a HVM via VT-d PCI passthrough. The IOMMU on my system seems to work, I can assign the PCI devices to my HVMs. The HVMs see the pci device and load their respective igb drivers, and ethtool -i eth0 works on each HVM, shows the drivers are loaded and the

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

I started a new thread because this not a pv-ops dom0 anymore. I''m running Andrew Lyon''s 2.6.31-4 patches for a non-pv-ops kernel. Got it again, after issuing "poweroff" from the domU. (XEN) (XEN) NMI - MEMORY ERROR (XEN) ----[ Xen-3.5-unstable x86_64 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff82c48011f55c>] remove_from_heap+0x8f/0xd0

Hi people. I had finally cross my USB to my DomU windows XP, justs 1 issue: USB 2.0 not working only 1.1 is working. I would to confirm with others that have the MoBo ASUS M4A89TD Pro/USB3 if u have been able to passthrough the USB ports to HVM windows? I had try different settings on my BIOS, different settings on Xen 4.1, this under Centos x64 AMD Athlon II 640. I receive the

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.

I recently managed to get PCI Passthrough to work for a Windows HVM operating under Xen 3.2 on Fedora 8. I needed to get USB ports passed through to the Windows VM with full hot plug functionality and I was able to get that working using a Dell 755 with a USB PCI expansion card. However, when trying to bring the box up to an operational status status I have encountered some rather severe

Hi : I am trying to do PCIe passthrough on HVM domu. I have window XP as a HVM domu and xen-4.0. dom0 and domU (without device assign) works fine. I have more than one NIC card. I want to passthrough 03:00.0 to domu here are the list of my nic cards: lspci | grep -i eth 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

Dear Users, in my case, i want to passthrough a pci-e graphiccard to a hvm guest. In the bios i have to select whether the onboard graphic is used as primary vga output or the pci-e one. If i define the onboard one then the pci-e card gets unavailable in xen, furthermore lspci did not show it anymore. if i set the pci-e card as primary, it comes up fine in xen, but if i hide that card which is

Hi, I have just applied IGD VGA Passthrough patches to Xen 4.4-unstable changeset 27238. Please refer to the 2 attached patches. 1. [Xen-devel] [PATCH 2/3] V4 qemu-xen-trad: Correctly expose PCH ISA bridge for IGD passthrough Link: http://lists.xenproject.org/archives/html/xen-devel/2013-06/msg01720.html 2. [Xen-devel] [PATCH 3/3] qemu-xen-trad: IGD passthrough: Expose vendor specific pci

Hi, I have just applied IGD VGA Passthrough patches to Xen 4.4-unstable changeset 27238. Please refer to the 2 attached patches. 1. [Xen-devel] [PATCH 2/3] V4 qemu-xen-trad: Correctly expose PCH ISA bridge for IGD passthrough Link: http://lists.xenproject.org/archives/html/xen-devel/2013-06/msg01720.html 2. [Xen-devel] [PATCH 3/3] qemu-xen-trad: IGD passthrough: Expose vendor specific pci

Hi, I was wondering if it is possible to passthrough to a HVM guest a PCI without IOMMU support using PV on HVM drivers in the guest. While trying creating the domain I received the following message: Error: failed to assign device: maybe the platform doesn''t support VT-d, or VT-d isn''t enabled properly? Is there any technical reason why this is impossible, or it just

On Xen-3.4 (unstable version), I have created CentOS HVM guest & WS2K8 HVM guest and dedicated MegaRAID SAS controller but I am not able to see the disk which is connected to MegaRAID SAS controller when I do fdisk -l (vtd support is enabled in Xen). Looks like the pci device(MegaRAID SAS controller) is getting dedicated successfully as I can see the device in the list of pci devices shown by

After upgrading from xen 3.2.x to xen 3.3.0 I get an error message when using pci passthrough with pv guests (my system is not vt-d enabled): xm create -c /etc/xen/domU/myguest Using config file "/etc/xen/domU/myguest". Error: pci: 0000:0e:05.0 must be co-assigned to the same guest with 0000:0f:0a.0 Sharing diffrent pci devices behind a pci bridge used to work in older xen versions for

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

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

Hi, all I''m trying SRIOV with Xen but failed to pass through virtual function of SRIOV to dom-U. My platform: Xen-unstable 4.2 Pvops Dom-0 kernel 2.6.32.35 CentOS 5.4 Dom-0 CentOS 5.4 HVM Dom-U And follow VtdHowto wiki page, my steps are: First, bind the virtual function to pci-stub. After that, check the assignable virtual function devices: [root@localhost ~]# xm