similar to: Status of FLR in Xen 4.4

The attached patches allow the pciback module to perform a reset whenever a PCI device is: - attached to the pciback module, as so: echo "0000:01.07.0" > /sys/bus/pci/devices/pciback/bind - detached from the pciback module, as so: echo "0000:01.07.0" > /sys/bus/pci/devices/pciback/unbind - and when the guest is done with (internally when the guest is not using

Hi As we will use xl in xen 4.1. I had try use xl to do something. And I find some command is fails. For config file, when give "disk=" too args, it will show segment fault if we use xl create to start guest. Is there any change for xl''s config file? Following command can not work: xl migrate: when I use xl migrate domain localhost to do migrate, it shows error:

Hi, all, The attached patches try to improve the current FLR logic. The idea is: removing the FLR logic from hypervisor and adding the improved logic in Control Panel. The current FLR logic in hypervisor has some issues: 1) Dstate transition is not guaranteed to properly clear the device state; 2) the current code for PCIe FLR is actually buggy: PCI_EXP_DEVSTA_TRPND doesn''t mean the

Hi there, I have a question regarding PCI passthrough on the Citrix XenServer 5.6 (Xen 3.4.2). I already managed to get some soundcard passed through to a Windows guest. So I think my knowledge about that topic isn''t _that_ low. But I cannot seem to pass through a SATA/PATA controller to a Linux guest. I have some additional CD/DVD burner (PATA) attached to a SATA/PATA controller

Hi all!. First of all sorry about my English it''s not very fluid. I have a small server based upon Supermicro X7DBN (Chipset Intel® 5000P) motherboard and Intel Xeon E5320 (1,83Ghz) with 4Gb of FB-DIMM RAM. The OS is Debian Lenny in dom0 (2.6.26-2-xen-amd64) and Debian Lenny in domU (2.6.26-2-xen-amd64). Xen is 3.4.2 compiled from sources. The problem comes when I need to passthrough

Aloha! Concisely, I''ve been trying for several days to get VGA/PCI passthrough working. Regarding VGA vs PCI passthrough, I''m not entirely certain of the difference? Does Xen perform a different set of operations when passing through a VGA card versus any PCIe card? I''ve read the wiki and it seems the answer is "yes;" however, when passing through a

First, maintainer''s addresses (Ryan Wilson <hap9@epoch.ncsc.mil>, Chris Bookholt <hap10@epoch.ncsc.mil>) are wrong (users unknown to remote mailsystem), so posting to you: PCI bus format strings are wrong. "%04x:%02x:%02x.%d" should be used instead of "%04x:%02x:%02x.%1x" (in many places of linux+v3.2.1/drivers/xen/xen-pciback/pci_stub.c) --

I''ve just had my first attempt at getting VGA passthrough to work, and it crashed the machine. I''m trying to understand whether this is a problem with my hardware, configuration or a software problem. I''m running Xen 4.1.2 with Linux 3.1.2 The CPU is an Intel Core i5-650 http://ark.intel.com/products/43546/Intel-Core-i5-650-Processor-%284M-Cache-3_20-GHz%29 The Video

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

Hello, I've been consistently attempting to make the setup mentioned in the subject work on the following hardware: Xeon E3 1275 (v1, Sandy Bridge) Asus P8B WS (Firmware: 0904 and 2009) 16 GB RAM Sapphire Radeon HD 7950 OC (Firmware: 015.013.000.010.000705) Linux 3.4.1 dom0, x86-64, pvops. Xen 4.1.2 (+ security patch) and 4.1.3-rc1. Old qemu-dm setup. (not new mainline qemu) Windows 7 64-bit

Hello everyone, i just updated from 4.2.1 to 4.2.2. If i try to fire up my win2k8 domU with a pci device attached, the dom0 machine hardcrashes. my system log (idrac) shows the following: CPU 2 has an internal error (IERR). A bus fatal error was detected on a component at bus 0 device 0 function 0. CPU 1 machine check detected. and plenty of other entries. The machine hardresets then. If i

Hello, i''m using the latest Xen 4.0 testing from the mercurial repository and i want to passthrough my Intel Core gpu. But somehow it has a weird IRQ of 1251. So i cant start the vm if i set pci=[''00:02.0'']. The device is bound to the pciback driver correctly. The interesting part of xm dmesg (appears when i start the vm): (XEN) [VT-D]iommu.c:1484: d0:PCI: unmap bdf =

Hello, i''m using the latest Xen 4.0 testing from the mercurial repository and i want to passthrough my Intel Core gpu. But somehow it has a weird IRQ of 1251. So i cant start the vm if i set pci=[''00:02.0'']. The device is bound to the pciback driver correctly. The interesting part of xm dmesg (appears when i start the vm): (XEN) [VT-D]iommu.c:1484: d0:PCI: unmap bdf =

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Fix to return -ENOENT in the pcistub_device_find() and pci_get_drvdata() error handling case instead of 0(overwrite to 0 by str_to_slot()), as done elsewhere in this function. Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> --- drivers/xen/xen-pciback/pci_stub.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Fix to return -ENOENT in the pcistub_device_find() and pci_get_drvdata() error handling case instead of 0(overwrite to 0 by str_to_slot()), as done elsewhere in this function. Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> --- drivers/xen/xen-pciback/pci_stub.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3

I have successfully passed through a video card, network card, USB mouse, and USB keyboard to a MS Vista guest. That works well. I am trying to add another PCI device, such as a audio card or PCI USB hub, but I am running into a strange problem. When I plug the PCI audio (or USB card) to the motherboard. It makes it so that the PCI video card is no longer an "assignable device" (xm

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. > > This bug was probably introduced in Debian Jessie sometime > > between

Thanks Anna, this was also quite interesting for me. Did you mean that I just have to eliminate the else branch or raise arround "All devices behind the uppermost PCI/PCI-X bridge must be co-assigned to the same guest." or do I have to eliminate more in order to prevent an FLR (whatever that is). For my board it''s definitely necessary to move PCI devices in different guests,

Hi All, Please help me. I am now installing the XEN on my PC and trying to config the pci pass through. My motherboard is intel DQ45CB which is vtd enabled. I downloaded the latest xen4.0 source from xen.org which is the latest release. I downloaded stable-2.6.32-x dom0 kernel source from jeremy''s repository. After compiling the xen and dom0 kernel, I could play it. I could create

Hi All, Please help me. I am now installing the XEN on my PC and trying to config the pci pass through. My motherboard is intel DQ45CB which is vtd enabled. I downloaded the latest xen4.0 source from xen.org which is the latest release. I downloaded stable-2.6.32-x dom0 kernel source from jeremy''s repository. After compiling the xen and dom0 kernel, I could play it. I could create