WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] [Fwd: Exporting USB /USB-PCI-Device to DomU]

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] [Fwd: Exporting USB /USB-PCI-Device to DomU]
From: Joti Mail <joti.mail@xxxxxxxxx>
Date: Fri, 01 Aug 2008 02:57:40 +0200
Delivery-date: Thu, 31 Jul 2008 17:58:28 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=RkKbBKQAbthe0TZ4ln3rGqBLt2abtwZUR0csMr8DyhY=; b=ns6NE5NNVza7ZsM0k64nivy4BpnkKUa57VNfb7x1D58efgnRGj+npTR7iFZ4dB7f3m kOCzdLQAGjKYMCTCrEa/j9DwYJZgXt34KQyk5ZeTcrL4p1QFvcQyrj5MlNq4yCdx3XCv 0n7hOg9NMXg8JyITlxoTt/gj/OCXDIVsR9z+s=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=aUR2IVHRZjvJ8wwfLcFLyCn3R14za4xTUo7I+F9lcl6f4YmD8EKhLaUIG40Nql3KHh sXwsOYPfNs1IceLmLz28L2eL5HN7tiqC9lEN3lvWSV6Y4SEa1pBLZT8xaimpNXFR8KZ+ EtsXDAvQkTlobDuUjHgJ/lpFYYp3WYbK7xPRA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.16 (Windows/20080708)
Hello,

some news to it:
I tried to manually unbind the driver (ohci_hcd) from the usb hub's slot and then tried to rebind it with Xen. That worked. After a restart of the DomU the USB-Hub and the Gigaset were recognized.

In that case i'ld rather regard the problem as solved.

Regards,
Johannes

-------- Original-Nachricht --------
Betreff: Exporting USB /USB-PCI-Device to DomU
Datum: Fri, 01 Aug 2008 02:19:14 +0200
Von: Joti M.
An: xen-users@xxxxxxxxxxxxxxxxxxx

Hello xen-users!

this evening I've been trying to get a Sinus 45 USB Dect Base-station to
run in a DomU to be usable with VBox and stuff.

The Sinus loads in the Dom0 fine with the gigaset and bas_gigaset
modules included in the kernel.

[   21.745129] gigaset: Hansjoerg Lipp <hjlipp@xxxxxx>, Tilman Schmidt
<tilman@xxxxxxx>, Stefan Eilers
[   21.745274] gigaset: Driver for Gigaset 307x
[   21.797616] usb 2-1: gigaset_probe: Device matched (Vendor: 0x681,
Product: 0x1)
[   21.797802] usbcore: registered new interface driver bas_gigaset
[   21.797898] bas_gigaset: Tilman Schmidt <tilman@xxxxxxx>, Hansjoerg
Lipp <hjlipp@xxxxxx>, Stefan Eilers
[   21.798014] bas_gigaset: USB Driver for Gigaset 307x

I've retrieved the PCI/Slot-Address of the USB-Hub the Sinus is
connected with and have added it to GRUB's menu.lst with pciback.hide

pciback.hide=(03:07.0) (00:12.1)
(The 03:07.0 is for a different device which works fine in a DomU)


00:12.1 USB Controller: ATI Technologies Inc Unknown device 4398
(prog-if 10 [OHCI])
        Subsystem: Elitegroup Computer Systems Unknown device 1b61
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
        Memory at fe7fd000 (32-bit, non-prefetchable) [size=4K]

Bus 002 Device 004: ID 0681:0001 Siemens Information and Communication
Products


The point is that in /sys/bus/pci/drivers/pciback/ there is no new slot
'directory' entry for that hidden device. The driver still loads
perfectly in the Dom0.

If I try to create new slot via echo bus:major:minor:device it works, I
get a new slot (listed in slots) but if I try to bind it then i get
"-bash: echo: write error: No matching device found"

If I then try to include it a domU configuration file via pci =
['00:12.1'] the domU boots, but no pci or usb or gigaset is reconized by
the domU.

(I can load the modules for usb, gigaset and so on fine, but they do not
bind to any hardware)


In my desperation I've even tried various parameters that were suggested
rather for HVM DomU use:


usb = [ 'path=2-1' ]
usb = [ 'path=2-4' ]

usb=1
usbdevice=[ 'host:0681:0001' ]

pci = [ '00:12.1' ]

The system everything runs on is:
Debian Etch + Backports x64 + .24-19 Kernel from Ubuntu 8.04 (otherwise
no atl1 driver)
Xen 3.2.1
DomU: Ubuntu 8.04 x64

Does anyone have any idea on how I could get a the USB device or the
USB-Hub exported to the DomU?

Any comments are highly welcome and appreciated :)

Thanks in advance!

Regards,
Joti

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] [Fwd: Exporting USB /USB-PCI-Device to DomU], Joti Mail <=