From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Error connecting USB-device to DomU, kernel 2.6.32-5-xen-amd64, Xen 4.0.1 Date: Tue, 1 Mar 2011 11:04:01 +0200 Message-ID: <20110301090401.GC5345@reaktio.net> References: <4D6CA92C.4080303@woefdram.nl> <20110301084553.GB5345@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20110301084553.GB5345@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Hans van Zijst Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Mar 01, 2011 at 10:45:53AM +0200, Pasi K=E4rkk=E4inen wrote: > On Tue, Mar 01, 2011 at 09:07:08AM +0100, Hans van Zijst wrote: > > Hi, > >=20 > > When trying to connect my USB printer to the DomU that has CUPS > > installed, I run into an error: > >=20 > > Unexpected error: > >=20 > > 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 ma= in > > _, rc =3D _run_cmd(cmd, cmd_name, args) > > File "/usr/lib/xen-4.0/lib/python/xen/xm/main.py", line 3644, in _r= un_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 devic= e > > info: Can't get assignment status: (5-2). > >=20 > >=20 > > I'm running Xen 4.0.1 on Debian Wheezy, kernel 2.6.32-5-xen-amd64, bo= th > > on Dom0 and the DomU. > >=20 > > I tried adding this line to the DomU's configuration: > >=20 > > vusb =3D [ 'usbver=3D2,numports=3D2,port_1=3D5-2,port_2=3D5-3' ] > >=20 > > 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. > >=20 > > After the DomU has booted, I issue "xm list-usb domu" on Dom0, which > > gives me: > >=20 > > 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 > >=20 > > 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 i= t, > > it bails out with: > >=20 > > unable to initialize libusb: -99 > >=20 > > Manually loading the usbcore module and its friends doesn't help. > >=20 > > Now, if I explicitly connect this thing with: > >=20 > > xm usb-attach DomU 0 1 5-2 > >=20 > > I get the error mentioned above. > >=20 > > Any ideas? > >=20 >=20 > I don't think Debian Squeeze 2.6.32 kernel includes Xen PVUSB support/p= atches. >=20 Basicly you need xen-usbback driver in the dom0 kernel and=20 xen-usbfront driver in the domU kernel. http://wiki.xen.org/xenwiki/XenUSBPassthrough See here for a pvusb patch for 2.6.32 pvops kernel: http://lists.xensourc= e.com/archives/html/xen-devel/2011-01/msg00354.html -- Pasi