From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] USB over network
Date: Mon, 06 Oct 2008 08:41:25 -0500 [thread overview]
Message-ID: <48EA1585.90804@codemonkey.ws> (raw)
In-Reply-To: <ED2414DB5FBBCF4FA66ECE71F290E9A2B601F5@EXVBE011-2.exch011.intermedia.net>
Gal Hammer wrote:
>> Apart from anything else, it's missing documentation.
>>
>
> I am aware of that. I'll document the work I've done so far and include
> the open issues that you (and others) wrote.
>
>
>> It looks like you have to start qemu with magic options on the remote
>> machine?
>>
>
> No, qemu should be started with "-usbremote host:port" command line
> option. This will start a listener which wait for incoming remote
> connections. The remote connection is established with the qemu-usbd
> application. The qemu-usbd is executed on the local machine, the one
> that the USB device is attached to.
>
I think it would be better to support a push instead of a pull model.
For instance, something like:
-usbdevice remote:host:port
That connected to something that was listening on the machine that had
the USB device. If you really wanted a server, I'd suggest a syntax like:
-usbdevice remote:host:port,server
So at a high level, what's functional now, and how much work is needed
to be completely functional? Is there anything that isn't going to work
because of fundamental issues?
Regards,
Anthony Liguori
> Gal.
>
>
>
>
next prev parent reply other threads:[~2008-10-06 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 11:43 [Qemu-devel] [PATCH] USB over network Gal Hammer
2008-10-06 12:09 ` Paul Brook
2008-10-06 12:22 ` Paul Brook
2008-10-06 12:42 ` Dor Laor
2008-10-06 13:15 ` Gal Hammer
2008-10-06 13:32 ` Paul Brook
2008-10-06 13:41 ` Anthony Liguori [this message]
2008-10-06 14:20 ` Gal Hammer
2008-10-06 15:24 ` Alexander Graf
2008-10-06 12:32 ` Daniel P. Berrange
2008-10-06 15:05 ` Blue Swirl
2008-10-07 8:34 ` Gal Hammer
2008-10-07 18:08 ` Blue Swirl
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=48EA1585.90804@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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).