similar to: pcifront pci-0: pciback not responding (tg3)

Hi all, I have been having an issue for over a year with several Xen installations and have not been able to find out if this is just something I am missing. Basically I am trying to configure a firewall with two ethernet cards in a domU using pci passthrough. I am hiding the Ethernet cards at boot time via the pciback.hide kernel option. Right now I am running Xen 3.3.0 and the two Ethernet

Following 7 patches are for PCIE AER (Advanced Error Reporting) support for XEN. --------------------------------------------------------------------------- Patches 1~4 back port from Linux Kernel which enables kernel support to AER. Those patches enable DOM0 PCIE error handling capability. When a device sends a PCIE error message to the root port, it will trigger an interrupt. The irq handler

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, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hello, The topic is self-explanatory: how to ensure that a PV driver domain correctly prepares its PCI devices for S3 sleep? If I do "pm-suspend" in dom0, and the driver domain has active network interfaces, suspend hangs the system. Yes, in case of this particular machine, suspend works fine when there is no driver domain. It is possible to manually invoke scripts from

Hi , I have been trying to understand PCI -passthrough support. Please correct me if I am wrong in my following inferences. 1. Device emulation and pass through are both implemented using split drivers. 2. But, in case of emulation drivers of dom0 are used where as in case of passthrough ( as the name suggests ) native drivers in domU are used . 3. dom0 provides a virtual PCI device { an

Hi , I have been trying to understand PCI -passthrough support. Please correct me if I am wrong in my following inferences. 1. Device emulation and pass through are both implemented using split drivers. 2. But, in case of emulation drivers of dom0 are used where as in case of passthrough ( as the name suggests ) native drivers in domU are used . 3. dom0 provides a virtual PCI device { an

Hi, I am trying to set up a Xen server using two 4-port NIC cards. The exact type: D-Link DFE 580TX. There are no problems using this cards under plain linux. The driver is called ''sundance''. But when I use pciback.hide the DomU can''t access this card. I have had the same task when using the NIC BCM 5708 (NetXtreme II). I had found a message in

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

testing, uname -ri 2.6.33-rc5-4-xen x86_64 rpm -qa | grep -i Xen-4 xen-4.0.0_20873_01-29.1.x86_64 cat test.cfg name = ''test'' builder = ''linux'' bootloader = ''/usr/lib/xen/boot/domUloader.py'' bootargs = ''--entry=xvda1:vmlinuz-xen,/boot/initrd-xen'' disk = [

Hi all! I want to assign a physical network card (e100) to a domU: I think Dom0 is ok but domU does not recognize the pci nic. into DomU I don''t know wath should I see: I have nothing in dmesg nor in messages... Into Dom0 I have this modules.conf: options pciback hide=(0000:03: 08.0) install e100 /sbin/modprobe pciback; /sbin/modprobe --ignore-install e100 This is dmesg: pciback

I am working on S5000VSA Intel Server Board with the following cpu spec. XEN-PEER-RHEL5 $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU E5345 @ 2.33GHz stepping : 7 cpu MHz : 2327.512 cache size : 4096 KB physical id : 0 siblings : 1 core id : 0

On Wed, Jun 22, 2016 at 11:49 AM, Francis Greaves <francis at choughs.net> wrote: > More information... > I have pcifront showing as a module in the DomU and the usb shows in dmesg > as: > [ 3.167543] usbcore: registered new interface driver usbfs > [ 3.167563] usbcore: registered new interface driver hub > [ 3.167585] usbcore: registered new device driver usb >

Hello, on a Supermicro H8DGU server with the latest BIOS PCI passtrough fails. I tried to give a two igbvf devices to the domU. pciback is configured and everything locks good until igbvf tries to initialize the PCI device. I have the same error with XEN 4.3, 4.3.1 and the current 4.4-unstable, linux kernel 3.12.0, 3.12.1, 3.9. DomU config: kernel = "/boot/gentoo-DomU" memory =

Hi! I am trying to export a PCI device (an AVM Fritzcard PCI ISDN card...) to a domU but when starting my domU I am getting this error: "pciback pci-4-0: 22 Couldn''t locate PCI device (0000:00:06.0)! perhaps already in-use?" My system is running both debian etch in dom0 and domU... Below you can find (hopefully) all important information... Sincerely, Gaubatz Patrick

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

I am a bit confused on the PCI stuff. PASSTHRU-- does this mean that pcifront is not needed? Or only that the PCI is not limited as it is with slot. In general, none of the docs are getting me anywhere with xen 3.0.3. Example: I run this: echo -n 0000:2:0.1>/sys/bus/pci/drivers/pciback/new_slot echo -n 0000:2:0.0>/sys/bus/pci/drivers/pciback/new_slot echo -n bind 0000:2:0.0 >

Hi all, did somebody successfuly export ISDN Cards to DomU? I want to have 2 ISDN Cards in DomU (for Asterisk with mISDN) lspci -vt -[0000:00]-+-00.0 nVidia Corporation MCP55 Memory Controller +-01.0 nVidia Corporation MCP55 LPC Bridge ... +-05.1 nVidia Corporation MCP55 SATA Controller +-06.0-[0000:01]--+-00.0 Cologne Chip Designs GmbH ISDN

Further to my messages back in May I have at last got round to trying to get my DomU to recognise USB devices. I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64. I have to manually make the port available before creating the DomU by issuing the command: xl pci-assignable-add 00:1a.0 otherwise nothing shows in: xl pci-assignable-list I have added this to my .cfg file as per the