qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: yuan.zhong@zte.com.cn
Cc: afaerber@suse.de, pbonzini@redhat.com, qemu-devel@nongnu.org,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: [Qemu-devel] New function: Remot USB support in qemu
Date: Thu, 27 Apr 2017 09:07:16 +0200	[thread overview]
Message-ID: <1493276836.31995.38.camel@redhat.com> (raw)
In-Reply-To: <201704271430117024953@zte.com.cn>

On Do, 2017-04-27 at 14:30 +0800, yuan.zhong@zte.com.cn wrote:
> Mr. Hoffmann,
> 
> 
> Thank you for your time.
> 
> 
> This email will describe a new module that I'd like to commit to the
> qemu code source.
> 
> We call it as remote usb, and this is features:
> 
> 1. real usb device is aside on a windows client.
> 
> 2. keeping a connection between the client and the VMs host OS
> 
> 3. qemu simulate a remote usb device through our remote usb module
> 
> 4. the communication between real usb device and the simulation remote
> usb is based on USB/IP protocol.

qemu supports that already.  It's called usb redirection.
https://www.spice-space.org/page/UsbRedir
https://github.com/SPICE/usbredir

usb redirection can use either plain tcp or a spice channel as
transport.  The spice client supports usb devices on windows clients.

Hans (Cc'ed, usbredir author) looked at the USB/IP protocol and found a
number of deficits and decided to not use it because of that.  I don't
remember the details though.

So I think using the existing usb redirection support is the better
option for you.

cheers,
  Gerd

      reply	other threads:[~2017-04-27  7:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27  6:30 [Qemu-devel] New function: Remot USB support in qemu yuan.zhong
2017-04-27  7:07 ` Gerd Hoffmann [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=1493276836.31995.38.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=afaerber@suse.de \
    --cc=hdegoede@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yuan.zhong@zte.com.cn \
    /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).