From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans van Zijst Subject: Error connecting USB-device to DomU Date: Mon, 28 Feb 2011 21:04:26 +0100 Message-ID: <4D6BFFCA.1080306@woefdram.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi, When trying to connect my USB printer to the DomU that has CUPS installed, I run into an error: Unexpected error: Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-4.0/bin/xm", line 8, in main.main(sys.argv) File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3620, in main _, rc = _run_cmd(cmd, cmd_name, args) File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3644, in _run_cmd return True, cmd(args) File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 2868, in xm_usb_attach if vusb_util.bus_is_assigned(bus): File "/usr/lib/xen-4.0/lib/python/xen/util/vusb_util.py", line 275, in bus_is_assigned raise UsbDeviceParseError("Can't get assignment status: (%s)." % bus) xen.util.vusb_util.UsbDeviceParseError: vusb: Error parsing USB device info: Can't get assignment status: (5-2). I'm running Xen 4.0.1 on Debian Wheezy, kernel 2.6.32-5-xen-amd64, both on Dom0 and the DomU. I tried adding this line to the DomU's configuration: vusb = [ 'usbver=2,numports=2,port_1=5-2,port_2=5-3' ] which supposedly creates 2 USB ports on the DomU (I found a document on the Internet describing PV-USB, but I can't find it anymore...). The first port, 5-2, is the one to which the printer is connected. After the DomU has booted, I issue "xm list-usb domu" on Dom0, which gives me: Idx BE state usb-ver BE-path 0 0 1 USB2.0 /local/domain/0/backend/vusb/14/0 port 1: 5-2 [ID 03f0:5511 HP Deskjet F300 series] port 2: 5-3 So far, so good. The Dom0 seems to hand the printer to the DomU. However, DomU doesn't seem to notice anything. When I do "lsusb" on it, it bails out with: unable to initialize libusb: -99 Manually loading the usbcore module and its friends doesn't help. Now, if I explicitly connect this thing with: xm usb-attach DomU 0 1 5-2 I get the error mentioned above. Any ideas? Kind regards, Hans