similar to: [PATCH 2/5] pciback: per-device permissive flag

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

Hello, I need to activate the permissive parameter for a asterisk PCI card. But this parameter doesn''t exist in /sys/module/pciback/parameters/ . I tried to activate this option in the boot option (pciback.permissive) ... When I want to use my PCI card in a domU : Nov 20 10:41:55 myhost kernel: pciback 0000:07:01.0: Driver tried to write to a read-only configuration space field at

Adds support for assigning a label to domains, obtaining and setting the current enforcing mode, and loading a policy with xl command and libxl header when the Flask XSM is in use. Adheres to the changes made by the patch to remove exposure of libxenctrl/libxenstore headers via libxl.h. tools/libxl/libxl_flask.c | 71 ++++++++++++++++++ tools/libxl/Makefile | 2

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

Fix formatting of Flask AVC audit messages so that existing policy tools can parse them. After applying, ''xm dmesg | audit2allow'' yields the expected result. Signed-off-by: Stephen D. Smalley <sds@tycho.nsa.gov> Signed-off-by: George S. Coker, II <gscoker@alpha.ncsc.mil> --- xen/xsm/flask/avc.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-)

Adds support for assigning a label to domains, obtaining and setting the current enforcing mode, and loading a policy with xl command when the Flask XSM is in use. libxl.c | 1 libxl.idl | 3 - xl.h | 3 + xl_cmdimpl.c | 171 +++++++++++++++++++++++++++++++++++++++++++++++++++++++--- xl_cmdtable.c | 18 +++++- 5 files changed, 187 insertions(+), 9

Hi all, I am trying to configure a Dom U to act as a firewall and therefore I need to pass one of the two ethernet cards to the Dom-U. I configured the Xen kernel to build pciback as a module and I am passing the hide option via boot parameters. I boot the pv machine via pygrub and I am able to see the ethernet device in Dom U as follows: Dom-U#lspci 02:00.0 Ethernet controller: Broadcom

I am trying to get a bt878 capture card working in Ubuntu 7.04 for a video surveillance application running on LAMP stack. It is based on Xen 3.0.3. Got all xm stuff working and apache/mysql/python working in domU. Now need access to /dev/Video0 I first tried pciback, where I get the following failure (from dom0 dmesg). (I blacklisted the bttv and related drivers). [ 0.198929] Kernel command

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

This patchset allows the user to define and manage groups of domains. The patch augments the xm utility with the following commands: grp-create, grp-shutdown, grp-destroy, grp-reboot, grp-pause, grp-unpause, grp-save, grp-restore, grp-join, and grp-migrate. A goal during development of group operations was to match support for common domain operations: create, shutdown, destroy, reboot, pause,

Hello everybody, for just one week I try to install three servers on an OpenSuSE 10.3 dom0 equipped with 4 NICs. One server is an OX using the onboard NIC via xenbr0. This server runs!! For my IPCop server I intended to use the three remaining NICs (Intel Pro100/S, 3Com 3C590, Realtek RTL-8139). These three NICs should be used natively by my IPCop. So I tried to use the pciback driver. I wrote a

I am using the latest xen unstable and trying to install this 00:19.0 Ethernet controller: Intel Corporation 82562V 10/100 Network Connection (rev 02) since xen uses 2.6.16.29 it does not support it yet, someone said (on google) that 2.6.18.3 supports it. So I want to boot 2.6.18.3 in domU and enable it with the pciback thing. my seize commands are: echo -n 0000:00:19.0 >

Hi, I am still trying to assign pci or usbs to a domU. I get to the point where pciback seizes the devices (5 usb and 2 pci). I modified the configuration of the domU with pci = [ ''00:1d.0'' , ''00:1d.1'' , ''00:1d.2'' , ''00:1d.3'' , ''00:1d.7'', ''02:01.0'' , ''02:02.0'' ] but

Remove duplicated #include('s) in drivers/xen/xen-pciback/xenbus.c Signed-off-by: Huang Weiyi <weiyi.huang at gmail.com> --- drivers/xen/xen-pciback/xenbus.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/xen/xen-pciback/xenbus.c b/drivers/xen/xen-pciback/xenbus.c index 206c4ce..978d2c6 100644 --- a/drivers/xen/xen-pciback/xenbus.c +++

Remove duplicated #include('s) in drivers/xen/xen-pciback/xenbus.c Signed-off-by: Huang Weiyi <weiyi.huang at gmail.com> --- drivers/xen/xen-pciback/xenbus.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/xen/xen-pciback/xenbus.c b/drivers/xen/xen-pciback/xenbus.c index 206c4ce..978d2c6 100644 --- a/drivers/xen/xen-pciback/xenbus.c +++

Good morning, I need to use pciback.hide to hide a pci card because I want to pci passthrough that card to a domU. My hardware neither supports Intel-Vt-d nor AMD's IOMMU. Unfortunately this doesn't seem to work in Centos 54 anymore. I guess it doesn't work because it is not compiled into the kernel, but as a module. I got the following error in dmesg and the pci device is still

Hello, I''m attempting to run Windows XP in a domU using the PCs actual graphics card. I believe I''ve set everything up correctly, including the pciback module etc. I''ve set pciback to grab the graphics card and all the USB hosts as well: (from dmesg) pciback 0000:00:02.0: seizing device pciback 0000:00:02.1: seizing device pciback 0000:00:1a.0: seizing device pciback

Hi, It seems that destroying pcifront/pciback always fails on current xen. This patch fixes the problem, making pciback switch to "Closed" state after pcifront switched to "Closing" state. Regards, ------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

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