similar to: PCI delegation works, access to the delegated NIC doesn''t

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

Hello, I am desperately trying to get pci-passthrough to working. I want to pass a tg3 nic to domU. when booting domU I get a lot of messages: pcifront pci-0: pciback not responding!!! in domU, "ifconfig eth... adress up" hangs for 2 minutes, finally ifconfig -a shows a correct setting with no data transmitted rx/tx The IP Adress is being assigned, but there is no data transmission

Hello, I've got a very strange problem. Lately I've been setting up my linux servers for network (layer2) redundancy with a bridge interface containing two ethernet interfaces connecting to two switches. So far I didn't have any problems with it, but now a very strange thing happens with a new server I'm installing. The server is an ibm x346 having two onboard BCM5721 cards, the

This patch enables PCI passthrough with stub domain. PCI passthrough with stub domain has failed in the past. The primary reason is that hypercalls from qemu in stub domain are rejected. This patch allows qemu in stub domain to call the hypercalls which is needed for PCI passthrough. For security, if target domain of hypercall is different from that of stub domain, it rejects hypercall. To use

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

Hello, is there any reason why even permissive devices cannot write some areas in the PCI config space? The PCI_COMMAND is handled in special way so that the device is enabled/disabled properly, am I right? Why is PCI_INTERRUPT_LINE read from dev->irq and not from the config space? Why the PCI address bars are handled in very different way? And it seems that writing these bars is never

Currently we assign devices with VT-d in Xend, this raises two issues: 1) assign devices regardless of they are hidden by pciback or not. If the device is not hidden, it results in the device doesn''t work in Dom0; 2) device is assigned one by one, if assign multiple devices, some devices may have been assigned when problem happens, it results in assigned devices don''t work in

Hi, I''m on a HP DL365, amd64, running SLES10sp1, but with kernel and xen of SLES10sp2, therefore using Xen 3.2. The domU shall be a Windows HVM guest. I want use the Qlogic SAN card in a domU. I''m following these instructions: http://www.novell.com/communities/node/2880/assign-dedicated-network-card-or-pci-device-xen-virtual-machine well, there is written that this only

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

Hi! I tried to pcipassthrough usb-controllers to domu to use it with a memory-stick. First xen complained that the driver needs write-access to its configuration space, so I added these to pci-quirks. Since it still didn''t work I also added the device to pci-permissive but I still get an errormessage with Oops (at the end of this email) when sticking in the memory-stick. I tried

Hi! I tried to pcipassthrough usb-controllers to domu to use it with a memory-stick. First xen complained that the driver needs write-access to its configuration space, so I added these to pci-quirks. Since it still didn''t work I also added the device to pci-permissive but I still get an errormessage with Oops (at the end of this email) when sticking in the memory-stick. I tried

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

I''m still playing around with xen-3.0.2-3 and the pciback.hide option. Currently I''m trying to give the guest a pcmcia-to-pci card with a prism54 wlan card in the slot. When starting the guest the following message apears in the bootlog: ... pciback 0000:02:09.0: can''t export pci devices that don''t have a normal (0) or bridge (1) header type! ... The lspci of

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

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! As dom0 I''m running Ubuntu Hardy withe xen 3.3 from backports. Reason to using xen 3.3 is that I could get Intrepid stock kernel to work as domu with xen 3.2. Now the problem I have is that I can''t passthrough PCI-devices to my domu. If I run lspci in the domu nothing is returned. I''ve tried to use the kernel from Hardy (2.6.24-21-xen) and stock kernel from

Hi! we have two Intel Quad Nic 82576, PCI ID 8086:10E8 and use the igb driver 1.3.19.3 on Debian 5.0.1. I used the pciback.hide XEN kernel parameter and made on of the NIC''s interfaces available in a DomU. Now, when I am starting the VM, the system crashes (log attached) I also tried to boot with the irqpoll option - the Interrupt Disabled message still appears when I try to start the

Hi, I have a Fedora 7 xen system with a domU to which I have delegated via pciback two isdn pci cards. One is a HFC-S card, the other a AVM Fritz!Card Pci 2.0. In the domU I load mISDN drivers for the cards. The two cards are recognized and function well UNTIL I either decide to unload one or both of the card driver modules (hfcpci and avmfritz) or I decide to shut down the domU. At this