From: Hans de Goede <hdegoede@redhat.com>
To: David Mansfield <spice@dm.cobite.com>
Cc: spice-devel@lists.freedesktop.org, Christoph Hellwig <hch@lst.de>,
qemu-devel@nongnu.org
Subject: Re: [Spice-devel] [Qemu-devel] usb redirection status report
Date: Fri, 21 Jan 2011 14:23:02 +0100 [thread overview]
Message-ID: <4D3988B6.4010505@redhat.com> (raw)
In-Reply-To: <1295554293.10753.18.camel@gandalf.cobite.com>
Hi,
On 01/20/2011 09:11 PM, David Mansfield wrote:
>> H
>> i,
>>
>> On 01/20/2011 12:27 PM, Christoph Hellwig wrote:
>>> On Wed, Jan 19, 2011 at 07:15:47PM +0100, Hans de Goede wrote:
>>>> Hi All,
>>>>
>>>> As most of you know I'm working on usb redirection (making client usb
>>>> devices
>>>> accessible in guests over the network).
>>>>
>>>> I thought it would be a good idea to write a short status report.
>>>>
>>>> So fat the following has been done:
>>>>
>>>> * written and posted a network protocol for usb redir. over the network,
>>>> and send this to the list.
>>>
>
> As another late-comer, hate to ask a possibly old question but will this
> added protocol allow usb devices from arbitrary "remote" hosts to be
> redirected or only from the host running the spice client?
>
Yes, the protocol is transport independent and there will be a standalone
usb-host implementation (an tcp/ip server daemon running a machine wishing
to "share" a usb device).
> I recently tried to use the native qemu usb functionality to
> pass-through a webcam and fell flat on my face due to what others
> described as "timing issues", and was wondering if it would be possible
> to pass a USB device plugged in to the vm-host to the vm-guest using
> your new functionality, even though a third (and unrelated) host is
> running the spice client.
For vm-host to vm-guest pass through it is best to use the existing
pass through support. I'm aware of the timing issues there, and I started
with fixing those before even thinking about doing usb redirection over
the network, see:
http://lists.gnu.org/archive/html/qemu-devel/2010-11/msg02527.html
For the first patch of my patch set fixing the timing issues for local
usb redirection. Tested with multiple webcams (usb iso mode input devices)
and a set of usb speakers (usb iso mode output device).
Unfortunately there has been little response to this patch set, so I've
no idea when it will get merged.
(this seems to be the story with a lot of qemu patch sets here on the list,
like Gerd's usb descriptor rehandling patches, maybe we need to review how
qemu's patch merging processes work?)
Regards,
Hans
next prev parent reply other threads:[~2011-01-21 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 18:15 [Qemu-devel] usb redirection status report Hans de Goede
2011-01-20 11:27 ` Christoph Hellwig
2011-01-20 18:50 ` Hans de Goede
2011-01-20 20:11 ` [Spice-devel] " David Mansfield
2011-01-21 13:23 ` Hans de Goede [this message]
2011-01-21 13:28 ` Alexander Graf
2011-01-21 13:33 ` Gerd Hoffmann
2011-01-21 13:41 ` Alexander Graf
2011-01-21 14:33 ` Gerd Hoffmann
2011-01-21 15:01 ` Alexander Graf
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=4D3988B6.4010505@redhat.com \
--to=hdegoede@redhat.com \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@lists.freedesktop.org \
--cc=spice@dm.cobite.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).