From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Hans van Zijst <hans@woefdram.nl>
Cc: xen-devel@lists.xensource.com
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 [thread overview]
Message-ID: <20110301090401.GC5345@reaktio.net> (raw)
In-Reply-To: <20110301084553.GB5345@reaktio.net>
On Tue, Mar 01, 2011 at 10:45:53AM +0200, Pasi Kärkkäinen wrote:
> On Tue, Mar 01, 2011 at 09:07:08AM +0100, Hans van Zijst wrote:
> > Hi,
> >
> > When trying to connect my USB printer to the DomU that has CUPS
> > installed, I run into an error:
> >
> > Unexpected error: <class 'xen.util.vusb_util.UsbDeviceParseError'>
> >
> > Please report to xen-devel@lists.xensource.com
> > Traceback (most recent call last):
> > File "/usr/lib/xen-4.0/bin/xm", line 8, in <module>
> > 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?
> >
>
> I don't think Debian Squeeze 2.6.32 kernel includes Xen PVUSB support/patches.
>
Basicly you need xen-usbback driver in the dom0 kernel and
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.xensource.com/archives/html/xen-devel/2011-01/msg00354.html
-- Pasi
prev parent reply other threads:[~2011-03-01 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 8:07 Error connecting USB-device to DomU, kernel 2.6.32-5-xen-amd64, Xen 4.0.1 Hans van Zijst
2011-03-01 8:45 ` Pasi Kärkkäinen
2011-03-01 9:04 ` Pasi Kärkkäinen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110301090401.GC5345@reaktio.net \
--to=pasik@iki.fi \
--cc=hans@woefdram.nl \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).