OK, PCI export working now.
Except that I still can't configure the bnep0 interface.
Hot plugging seems to work, but dmesg gives:
 SIOCSIFADDR: No such device
 bnep0: ERROR while getting interface flags: No such device
 SIOCSIFNETMASK: No such device
 bnep0: ERROR while getting interface flags: No such device
 Failed to bring up bnep0.
# lspci
.&checktime(0000,00,07,':').2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
# lsusb
Bus 001 Device 002: ID 0db0:1967 Micro Star International Bluetooth Dongle
Bus 001 Device 001: ID 0000:0000
# lsmod
Module Size Used by
bnep 12256 0
crc32 3808 1 bnep
l2cap 22340 1 bnep
videodev 7360 0
hci_usb 13928 0
bluetooth 44164 3 bnep,l2cap,hci_usb
uhci_hcd 30416 0
usbcore 107672 3 hci_usb,uhci_hcd
Any suggestions?
(Yes, I talk to myself in the blue room too !! :))
Marcus Brown wrote:
>Dear, oh dear!!
>
>pci = ['00,07,2'] in domU config!!!
>(I'm going blind, I think)
>
>doh!
>
>lol
>
>Marcus Brown wrote:
>
>
>
>>Hi all.
>>
>>I've been attempting to export the USB Host Controller to a domU,
>>so that I can use a USB Bluetooth adapter (and possibly a USB camera).
>>I've been using xen-testing on Debian (dom0 is sid, domU is sarge)
>>
>>I've managed to get the domU to boot using a few of the following settings:
>>
>> The kernel line in grub's menu.lst now includes:
>> physdev_dom0_hide=(00:07.2)
>> The domU kernel config has:
>> XEN --->
>> [*] Physical device access
>> [*] Block-device backend driver
>> [ ] Network-device backend driver
>> X86 Processor Configuration --->
>> Bus options (PCI, PCMCIA, EISA, MCA, ISA) --->
>> [*] PCI support
>> [*] Legacy /proc/pci interface
>> [*] PCI device name database
>> Device Drivers --->
>> Networking support --->
>> <M> Bluetooth subsystem support --->
>> --- Bluetooth subsystem support
>> <M> L2CAP protocol support
>> <M> SCO links support
>> <M> RFCOMM protocol support
>> [*] RFCOMM TTY support
>> <M> BNEP protocol support
>> [*] Multicast filter support
>> [*] Protocol filter support
>> <M> HIDP protocol support
>> Bluetooth device drivers --->
>> <M> HCI USB driver
>> [*] SCO (voice) support
>> <M> HCI VHCI (Virtual HCI device) driver 
>> Device Drivers --->
>> Multimedia devices --->
>> <M> Video For Linux
>> USB support --->
>> <M> Support for Host-side USB
>> [*] USB device filesystem
>> <M> UHCI HCD (most Intel and VIA) support
>> <M> USB STV680 (Pencam) Camera support
>>
>>After booting the domU, the USB modules can be loaded manually,
>>however, there are no PCI devices found, or USB devices listed.
>>
>>I have come to the conclusion (from the xen-users manual) that my
>>xend-config.sxp is in error. I've tried appending:
>> (backend (blkif))
>> (device (pci (bus 00) (dev 07) (func 2)))
>>
>>(this could explain why I now get errors from 'xm list -v' now:))
>>
>>but during boot of the domU I still get the following:
>> Starting hotplug subsystem:
>> pci
>> cat: /sys/bus/pci/devices/*/class: No such file or directory
>> cat: /sys/bus/pci/devices/*/vendor: No such file or directory
>> cat: /sys/bus/pci/devices/*/device: No such file or directory
>> cat: /sys/bus/pci/devices/*/subsystem_vendor: No such file or directory
>> cat: /sys/bus/pci/devices/*/subsystem_device: No such file or directory
>> Bad PCI agent invocation
>>
>>Can anyone see something obviously wrong here?
>>The users manual talks about placing these options
>>"somewhere within the vm element of its configuration"
>>but I'm unable to find information on how to do this.
>>
>>Thanks for any pointers,
>>
>>Marcus.
>>
>>_______________________________________________
>>Xen-users mailing list
>>Xen-users@xxxxxxxxxxxxxxxxxxx
>>http://lists.xensource.com/xen-users 
>> 
>>
>> 
>>
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-users 
>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users