similar to: Unknown boot option `pciback.hide=(09:04.0)': ignoring

Hi, next step, # dmesg | grep pciback Bootdata ok (command line is root=/dev/sda2 ro console=tty0 pciback.hide=(0000:02:05.0)(0000:02:06.0)(0000:02:07.0)(0000:02:08.0)(0000:02:09.0) ) Kernel command line: root=/dev/sda2 ro console=tty0 pciback.hide=(0000:02:05.0)(0000:02:06.0)(0000:02:07.0)(0000:02:08.0)(0000:02:09.0) Unknown boot option

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

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

All, I would like to run the following issue past the list to confirm that my problem analysis makes sense or whether I missed something: We have a HP ML370G6 server with VT-x and VT-d enabled in the BIOS. It is equipped with two Smart Array HBAs - one connected to the HDD array (SmartArray P800) and one connected to an LTO tape drive (SmartArray P212). Both controllers use the same driver

Hi there, After updating a server from CentOS 5.3 to 5.4 my Xen pci-passthru setup has some troubles. The server has two NICs, one used by dom0 and the other assigned to a domU and one SCSI controler assigned to another domU. It has been working fine since CentOS 5.1, when I did the initial setup. After upgrading to 5.4, I get this error when starting the domU with one of the NICs assigned:

Or how to delegate special PCI devices from domain-0 to dom(u) Hi, I tried to manage some pci devices for dom(u) domains, using the fedora core 5 (xen0/u) and 6-test2 (xen) i686 kernel-xen and kernel-xen-devel rpms: In domain-0 lspci shows the pci device 00:04.01 which should be delegated to dom(u) In dom(u) lspci does not show any information (this seems to be ok) lsmod in dom(u) gives:

Hi, I have successfully start my Win7 x86 domU on my x64 Xen dom0 system. Now I want to give my Win7 full access to my Nvidia card. lspci 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [Quadro NVS 140M] (rev a1) and I added these to my /etc/modprobe.d/xen-pciback.conf options xen-pciback hide=(0000:01:00.0) then I ran modprobe xen-pciback nothing happens on the screen, and my

Hi List, please excuse that this post is again about networking with XEN. Even though I googled and checked other posts for some days now I did not manage to get my installation working. Following some advises I used the late binding of pci. So I created a /etc/modprobe.de/local and added: options pciback hide=(03:00.0)(04:00.0) install e1000 /sbin/modprobe pciback ; /sbin/modprobe

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

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

Hi all, I made run some domU on my debian stable dom0 I got 2 NIC and I would like to attach my second NIC to a special dom0 (proxy) I read some docs about it, I add pciback.hide=(0a:02.0) on my menu.lst and I start my domU (proxy) like that. xm -create -c proxy pci=0a:02.0 I try with pci=[''0a:02.0''] on my domU conf file But none of this work for me. I use kernel

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

So yesterday I got was able to get a domU successfully using a PCI SCSI card. This morning I restarted the host server. When I try to start up the same domU I get this error: Error: pci: improper device assignment specified: pci: 0000:0e:04.0 must be co-assigned to the same guest with 0000:0e:04.0, but it is not owned by pciback. How do I make this card owned by pciback on reboot. Do I need to

Hi, once again, Problems with pciback and pci passthrough the system -------------------------------------------------------------------------------- DOMAIN0:~# lspci -tv -[0000:00]-+-00.0 nVidia Corporation nForce3 250Gb Host Bridge +-01.0 nVidia Corporation nForce3 250Gb LPC Bridge +-01.1 nVidia Corporation nForce 250Gb PCI System Management +-02.0

Hi all, I just installed centos 5.4 xen-kernel on intel core i5 machine as dom0. After some hours of syncing a raid10 array (8 sata disk) I noticed a steadily increasing loadavg. I think without reasonable i/o wait or cpu utilization the loadavg on this system should be very lower. If this loadavg is normal I would be greatful if somone could explain why. The screenshots below show that there is

This issue was brought up about a year and a half ago. So I''ll bring it up again and see if anything happens. I''ve got an infiniband network and am attempting to pass the infiniband card through the host and give it to the guest. I''m working with standard CentOS 5.2 on both guest and host with their provided xen (3.0.3 ish). I''ve also attempted to install the

This issue was brought up about a year and a half ago. So I''ll bring it up again and see if anything happens. I''ve got an infiniband network and am attempting to pass the infiniband card through the host and give it to the guest. I''m working with standard CentOS 5.2 on both guest and host with their provided xen (3.0.3 ish). I''ve also attempted to install the

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