From: George Dunlap <george.dunlap@citrix.com>
To: "Wei Liu" <wei.liu2@citrix.com>,
"Jānis Andersons | Failiem.lv" <ja@failiem.lv>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
"jgross@suse.com" <jgross@suse.com>,
Chun Yan Liu <cyliu@suse.com>,
xen-devel@lists.xen.org
Subject: Re: Unexpected error: <class 'xen.util.vusb_util.UsbDeviceParseError'>
Date: Tue, 12 Jan 2016 15:19:46 +0000 [thread overview]
Message-ID: <56951992.3090808@citrix.com> (raw)
In-Reply-To: <20160107102112.GA11369@citrix.com>
On 07/01/16 10:21, Wei Liu wrote:
> CC George (who does the packaging for CentOS)
>
> BTW this problem is better directed to appropriate mailing list of
> CentOS (centos-virt? I can't remember the exact name).
It would be centos-virt, but as it looks like an upstream bug, if Janis
had reported this there, I probably would have asked him to re-report it
here (or on xen-users).
> On Thu, Jan 07, 2016 at 10:53:00AM +0200, Jānis Andersons | Failiem.lv wrote:
>> xen_major : 4
>> xen_minor : 4
>> xen_extra : .3-3.el6
>> CentOS release 6.7 (Final)
>>
>> After:
>> xm usb-hc-create demo_win2012_r2 2 4
I'm actually a bit surprised this worked, as I didn't think the CentOS
Virt SIG kernel had PVUSB support. Which kernel are you using?
Chunyan / Juergen, what modules should he look for to see if he has
pvusb backend support?
>> xm usb-list demo_win2012_r2
>> WARNING: xend/xm is deprecated.
>> Idx BE state usb-ver BE-path
>> 0 0 1 USB2.0 /local/domain/0/backend/vusb/2/0
>> port 1:
>> port 2:
>> port 3:
>> port 4:
>> xm usb-list-assignable-devices
>> WARNING: xend/xm is deprecated.
>> 1-1 : ID 090c:1000 SMI Corporation USB DISK
>> 1-10 : ID 14dd:0002 Peppercon AG Multidevice
>>
>>
>> xm usb-attach demo_win2012_r2 0 1 1-1
>>
>> WARNING: xend/xm is deprecated.
>> Unexpected error: <class 'xen.util.vusb_util.UsbDeviceParseError'>
>>
>> Please report to xen-devel@lists.xen.org
>> Traceback (most recent call last):
>> File "/usr/sbin/xm", line 20, in <module>
>> main.main(sys.argv)
>> File "/usr/lib64/python2.6/site-packages/xen/xm/main.py", line 3946, in
>> main
>> _, rc = _run_cmd(cmd, cmd_name, args)
>> File "/usr/lib64/python2.6/site-packages/xen/xm/main.py", line 3970, in
>> _run_cmd
>> return True, cmd(args)
>> File "/usr/lib64/python2.6/site-packages/xen/xm/main.py", line 3011, in
>> xm_usb_attach
>> if vusb_util.bus_is_assigned(bus):
>> File "/usr/lib64/python2.6/site-packages/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: (1-1).
This could possibly be a side-effect of having no PVUSB backend; it
could also be a straight-up bug in xend.
If it's an issue with having no PVUSB backend, you could try to build a
kernel with support; the SLES kernel is probably your best bet, as I
*think* they officially support it.
If you have PVUSB available, then it's probably a bug in xend.
Unfortunately xend has been poorly maintained for some time. Xen 4.4 is
already out of support, and xend was removed from the tree shortly after
the Xen 4.5 development window opened (hence the warnings). So in this
case it would most likely be classified as WONTFIX.
PVUSB support for xl is 99% certain to be available for Xen 4.7.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-12 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 8:53 Unexpected error: <class 'xen.util.vusb_util.UsbDeviceParseError'> Jānis Andersons | Failiem.lv
2016-01-07 10:21 ` Wei Liu
2016-01-12 15:19 ` George Dunlap [this message]
2016-01-12 15:51 ` Juergen Gross
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=56951992.3090808@citrix.com \
--to=george.dunlap@citrix.com \
--cc=cyliu@suse.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ja@failiem.lv \
--cc=jgross@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).