[Xen-users] pciback vs. qemu-dm vs. ?

[John Williams <hogleg_willy@xxxxxxxxxxxxx>]

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 line: root=/dev/md0 ro console=tty0 
pciback.permissive pciback.hide=(02:02.0)(02:02.1)
[ 0.470768] pciback 0000:02:02.0: seizing device
[ 0.470833] pciback 0000:02:02.1: seizing device
[ 0.550322] ACPI: PCI Interrupt 0000:02:02.1[A] -> GSI 19 (level, low) 
-> IRQ 17
[ 0.550452] ACPI: PCI interrupt for device 0000:02:02.1 disabled
[ 0.550627] ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 19 (level, low) 
-> IRQ 17
[ 0.550756] ACPI: PCI interrupt for device 0000:02:02.0 disabled
[ 33.929548] pciback: vpci: 0000:02:02.0: assign to virtual slot 0
[ 33.929633] pciback pci-1-0: 22 Couldn't locate PCI device 
(0000:02:02.0)! perhaps already in-use?
[ 921.917377] ACPI: PCI interrupt for device 0000:02:02.0 disabled

So, first off, how can I debug what is failing on the domU handoff? Any 
way to get more informative dmesg or syslog messages. Are there other 
logs to look at? Looking at /sys, the 2 devices are linked under the 
pciback directory.
Secondly, thinking that giving a PCI card to the guest is not a good 
idea, got searching for a way to emulate the device, to preserve Dom0 
stability. Ran into the QEMU-DM discussion. So, will this capability be 
usable on para-virtualized non-VT enabled processors? How do we give 
users the capability to generically attach devices to Xen guests that do 
not run the newer processors?
John





_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users