similar to: [Fwd: Re: [Xen-users] Re: bt878 based dvr card vs. pci pass-thru]

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

Hello, I'm having a problem, I've seen other people with the same problem, but with USB. Some people solved this with the pciback.permissive option, but in my case it's ignored. I'm using CentOS 5.2 - 2.6.18-92.1.10.el5.centos.plusxen The error return from the console starting the domU is below. I've tried swiotlb=force, pciback.permissive like I said. My configs are:

Hello, I''m seeing problems with Xen and IRQ-sharing PCI cards which are passed through to a Xen DomU. As I''m not sure whether this is a problem with Xen or with the Debian Xen Kernel (2.6.26-13 from lenny) I''m using, I''d like to ask here before posting a bug. Reproducing the problem goes as follows: 1. Put a PCI card in the machine and make sure it shares

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

(please keep me on Cc when replying) I have a server running Xen that regularly spews the following. The box seems to survive fine regardless - just thought I''d let everyone know. Dec 8 12:19:26 server kernel: 0x47/0x7a Dec 8 12:19:26 server kernel: [alloc_skb_from_cache+70/243] alloc_skb_from_cache+0x46/0xf3 Dec 8 12:19:26 server kernel: [__dev_alloc_skb+70/92]

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 [

Florian, I read already here and there that you shall not use shared interrupts in different PV DomUs, although I never found a written statement. But behaviour is exactly as you described, thus I took care that cards that share an IRQ are in the same DomU/Dom0. I also selected my motherboards accordingly. When I lately discussed lately with someone about MSI, I had the hope this could help,

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

Once last night and the night before a XenU go into a Zombie state, requiring a reboot. I''m not quite sure what is happening, and am looking for advise on how to diagnose the problem. .. While writing this email, it crashed again. This time I had an ''xm console calcutta'' capturing the output. I read a suggestion in these archives suggesting that I can just

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

Hi, One of my servers has had its dom0 "oops" over and over twice in the last week. Unfortunately this is newly deployed so I have no idea if it is down to Xen or not. xen_changeset : Mon Dec 12 18:47:47 2005 +0100 8270:4ad23e798798 dom0 kernel is a vanilla 2.6.12 with Ralph''s .6+xen kernel patch applied. x86_32 sarge packages were used. The .config is

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

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

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 >

Hello, I have encountered a crash in dom0 kernel while booting a domU from an AOE device. I haven''t seen such crashes when booting from local partitions/ LVM volumes/ loopback file systems. Also I haven''t seen such crash when I did repetitive I/O to these AOE devices. As the call trace of crash indicates the crash is in xenolinux kernel. Also this crash is predictably

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

Hi, I'm trying to pass a physical network interface through to a domU. This seems to be impossible because the way xen wants to do it is incompatible with the way centos wants to do it. I followed documentation on http://www.xen-support.com/?p=151 and tried booting with 'pciback.permissive pciback.hide=(06:00.0)'. This gives a hint in dmesg "kernel: xen-pciback: backend is

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