similar to: [PATCH] pciback: Fix Destroying pcifront/pciback

When destroying pcifront/pciback, the following message appears in the guest linux kernel log. WARNING: g.e. still in use! WARNING: leaking g.e. and page still in use! This is caused by the wrong disconnect procedure that pcifront terminates the gnttab foreign access before pciback unmaps the ring. This patch corrects the handling of pcifront/pciback destruction sequence. Firstly pcifront

This is a small fix of the error handling in device_create(). Signed-off-by: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com> Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

Hi gurus, I used xen 4.1.0 (64bit) + dom0 kernel 2.6.32.39 (32bit) + domu kernel 2.6.32.39 (32bit) environment. I was trying to passthru Broadcom NIC to domu. The NIC can be UP but not RUNNING, on domu #ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:10:18:95:25:90 inet addr:10.0.0.3 Bcast:10.0.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1

Dear All, The production server supports Intel Virtualization Technology. Processor is an Intel Xeon 1.86 GHz Quad Core. 8 GB DDR2 memory. There is also an Emulex LightPulse Fiber Channel HBA adapter. The host operating system (Dom 0) is RHEL 5 x86 with Xen Virtualization technology. Dom 0 kernel is 2.6.18-8.el5xen. I have recompiled the Dom 0 kernel so that pciback

This patch enables ''xm pci-attach/detach'' commands to be executed via xen-api. Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Xend doesn''t correctly work after restart, when there is a domU which owns a pci device (driver domain). This patch fixes the problem. Regards, ------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Add direct pci device assignment support. This patch depends on the previous patch (1/3). ----------------------------------------- Fields for DPCI class: (RO_inst) VM PPCI hotplug_slot <- same as vslot param of pci-attach/detach. (RO_run) virtual_domain virtual_bus virtual_slot virtual_func virtual_name <- domain:bus:slot:func

Currently console class''s "other_config" parameters (such as "vnclisten" and "vncpasswd") are not passed to xend when creating a domain by xm command through xen-api. The attached patch fixes this problem. Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list

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,

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

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

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 >

include/xen/xenbus.h nicely declares struct xenbus_driver''s ''ids'' member as pointer to const... As usual, written and tested on 2.6.25-rc3 and made apply to the 2.6.18 tree without further testing. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2008-02-26/drivers/xen/blkback/xenbus.c

Hi , I am testing pcifront on freebsd domU using following sound card [ Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] Following sound driver is used for this sound card on Freebsd: *snd_csa*-- Crystal Semiconductor CS461x/462x/4280 PCI bridge device driver I am able to detect the card. pci3: <PCI bus> on pcib3 csa0: <CS4280/CS4614/CS4622/CS4624/CS4630> mem

Patch 6 pciback_err_handler.patch: Implementation for enabling PCIE_AER support in XEN This patch is the main implementation for enabling PCIE_AER handling, adding related pci error handler in pciback and pcifront. When a device sends a PCIE error message to the root port, it will triger an interrupt. The irq handler will then collect roor error status register, then schedule a work to process

hi,         I am  an engineer of Intel , on cloud and virtalization. thanks for you great updates of vTPM.Could you share your experience on how to build vTPM with xen 4.3?  I failed to boot up  2.6.18.8 kernel which is from               # make linux-2.6-xen-build              # make linux-2.6-xen-install                   I want to integerate  vTPM to OpenAttestation.OpenAttestation project is

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

Use new PCI interfaces to simplify xen-pcifront implementation: 1) Use pci_create_root_bus() instead of pci_scan_bus_parented() because pci_scan_bus_parented() is marked as __deprecated.This also gets rid of a duplicated call of pci_bus_start_devices(). 2) Use pci_stop_root_bus() and pci_remove_root_bus() instead of open-coded private implementation. 3) Use pci_set_host_bridge_release()

Use new PCI interfaces to simplify xen-pcifront implementation: 1) Use pci_create_root_bus() instead of pci_scan_bus_parented() because pci_scan_bus_parented() is marked as __deprecated.This also gets rid of a duplicated call of pci_bus_start_devices(). 2) Use pci_stop_root_bus() and pci_remove_root_bus() instead of open-coded private implementation. 3) Use pci_set_host_bridge_release()