similar to: pciback not working

Hi there, I have a question regarding PCI passthrough on the Citrix XenServer 5.6 (Xen 3.4.2). I already managed to get some soundcard passed through to a Windows guest. So I think my knowledge about that topic isn''t _that_ low. But I cannot seem to pass through a SATA/PATA controller to a Linux guest. I have some additional CD/DVD burner (PATA) attached to a SATA/PATA controller

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

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 >

server:~# dmesg|grep pciback [ 0.000000] Kernel command line: root=/dev/hda1 ro console=tty0 pciback.permissive pciback.hide=(00:1d.00)(00:1d.01)(00:1d.07) [ 0.000000] Unknown boot option `pciback.permissive'': ignoring [ 1.210945] pciback 0000:00:1d.0: seizing device [ 1.211082] pciback 0000:00:1d.1: seizing device [ 1.211215] pciback 0000:00:1d.7: seizing device [

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, some more info which I collected during physically accessing the machine while rebooting. I was suprised that while it was not able to do anything it was not a ''static'' kernel panic, but the following text was scrolling continously thru the screen: """ ata3: port reset, p_is 1 is e pis 1 cmd c017 tf 50 ss 113 se 0 ata3: status=0x50 { DriveReady SeekComplete }

Hi Lists, sorry for reposting this, but since no response has arrived so far and my time on this project is passing by I need to make a conclusion. Do I better use my DVR cards in dom0 or moving it to a separate physical machine rather than using them in a domU? Could someone shed light on why it is trickier to pass-thru one of these cards than any other pci devices? Do they try to read-write

Hi Lists, sorry for reposting this, but since no response has arrived so far and my time on this project is passing by I need to make a conclusion. Do I better use my DVR cards in dom0 or moving it to a separate physical machine rather than using them in a domU? Could someone shed light on why it is trickier to pass-thru one of these cards than any other pci devices? Do they try to read-write

With the kernel option ''xen-pciback.hide=(00:14.2) xen-pciback.permissive'', Xen-4.2.0-rc3 is unable to pass through my onboard Intel HDA audio adapter to a Windows7 guest. I tried doing the same in KVM and it worked immediately without issue. On the guest, I get a "High Definition Audio Controller" with the correct vendor/device ID, and an error of "This device

Hello everybody, I''m experiencing some problems while exporting a whole usb hub to my DomU. My Dom0 is a Debian Etch using Xen 3.2 and kernel 2.6.18-5-xen-686 SMP on an intel core 2 duo. My DomU is a CentOs 5.1 using same kernel. Both are 32 bits environnements. I''ve exported my Usb Hub, and a ethernet card, using the pciback.hide=(04:00.0)(00:1d.0) option to Dom0 kernel. I

Greetings Xen user community, I am interested in using Mellanox ConnectX cards with SR-IOV capabilities to passthrough pci-e Virtual Functions (VFs) to Xen guests. The hope is to allow for the use of InfiniBand directly within virtual machines and thereby enable a plethora of high performance computing applications that already leverage InfiniBand interconnects. However, I have run into some

Hi, I really need help. I spent 2 days already on this pci passthrough thing. I''m using Xen 3.2.1 with Centos 5.2 64 bits on intel VT. I''d like to use PCI passthrough and I don''t think I need VT-D functionality. I''m trying to pass PCI 12:01.0 to my domU guest. I got this error when I use "xm create /etc/xen/hvm_centos_2.cfg" Using config file

I've got a Digium PCI telephone card that I'm trying to use with an AsteriskNow guest, on a CentOS 5.2 host. I've tried setting up the pciback stuff, and think I've done it right, but the card does not show up in the guest. I'm obviously missing something, so any help (including ways to debug this!) would be greatly appreciated. Here's some more info: The guest is

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''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()

I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()

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

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

Hallo, the device is working without problems in the dom0, found from parport_pc: dmesg small2 snip: parport_pc: ITE8875 found (1P) parport0: PC-style at 0xf000 [PCSPP,TRISTATE,EPP] parport0: Printer, Kyocera FS-1700+ parport_pc: ITE 8872 parallel port: io=0xF000 parport1: PC-style at 0x378 [PCSPP,TRISTATE] snap to assign this device to a domU I gave the boot-parmaters