From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: "Dirk Winning, junidas GmbH" <dirk.winning@junidas.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: bug?
Date: Mon, 17 Feb 2014 16:51:54 +0200 [thread overview]
Message-ID: <20140217145154.GL2924@reaktio.net> (raw)
In-Reply-To: <E5A6B4A8-4185-4002-B7A9-3098ABED8A0E@junidas.de>
On Mon, Feb 17, 2014 at 11:28:55AM +0100, Dirk Winning, junidas GmbH wrote:
> Hi,
Hi,
> we have XEN 4.0.1 on debian 6.0.6
First of all you should upgrade Xen..
Xen 4.0.1 is very old already, and it's not supported anymore by upstream.
> and I tried to activate a USB-Modem for a DOMU running OSX; the modem is
> already recognized and looks right; but it will not dial out or take a
> call.
> Tried a memory-Stick and the same here: it appears in USB but will not
> mount.
> Obviously it may not be clear where the problem exactly is, but one
> question arises:
> is it neccessary to do all steps listed further down and what about the
> error message?
> Since, the USB-devices already do appear correctly, but are unusable in
> the end.
> Thanks for any hints
> greets
> Started domain fax (id=89)
> root@graff:~# xm usb-list 89
> root@graff:~# xm usb-hc-create fax 89 1
> root@graff:~# xm usb-list 89
> Idx BE state usb-ver BE-path
> 0 0 1 USB2.0 /local/domain/0/backend/vusb/89/0
> port 1:
> root@graff:~# xm usb-add 89 host:05ac:1401
> root@graff:~# xm usb-list 89
> Idx BE state usb-ver BE-path
> 0 0 1 USB2.0 /local/domain/0/backend/vusb/89/0
> port 1:
> root@graff:~# xm usb-attach 89 0 1 2-1
>
Hmm.. "usb-attach" is a command for Xen PVUSB.
Do you really have a Xen PVUSB backend driver (usbback) in dom0 kernel,
and especially PVUSB frontend driver loaded in the *OSX* VM?
-- Pasi
> Unexpected error: <class 'xen.util.vusb_util.UsbDeviceParseError'>
> Please report to [1]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: (2-1).
> root@graff:~# xm usb-list-assignable-devices
> 1-6 : ID 14dd:0002 Peppercon AG Multidevice
> 2-1 : ID 05ac:1401 Motorola, Inc. Apple USB Modem
> 2-2 : ID 06da:0003 OMRON USB UPS
> Dipl. Ing. Dirk Winning, Systemberater
> [2]dirk.winning@junidas.de
>
> junidas GmbH, Aixheimer Str. 12, 70619 Stuttgart
> Tel. +49 (711) 4599799-12
> Geschäftsführer: Dr. Markus Stoll, Matthias Zepf
> Amtsgericht Stuttgart, HRB 21939
>
next prev parent reply other threads:[~2014-02-17 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 10:28 bug? Dirk Winning, junidas GmbH
2014-02-17 14:51 ` Pasi Kärkkäinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-23 10:32 Bug? Dirk Winning
2012-11-23 16:46 ` Bug? George Dunlap
2010-02-26 11:15 Bug ;( Ян Программист
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=20140217145154.GL2924@reaktio.net \
--to=pasik@iki.fi \
--cc=dirk.winning@junidas.de \
--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).