From: Michal Novotny <minovotn@redhat.com>
To: Dhananjay Goel <dhananjaygoel123@gmail.com>
Cc: James Harper <james.harper@bendigoit.com.au>,
xen-devel@lists.xensource.com
Subject: Re: Virtualization project idea
Date: Fri, 27 Aug 2010 16:20:53 +0200 [thread overview]
Message-ID: <4C77C9C5.1010307@redhat.com> (raw)
In-Reply-To: <AANLkTikZi6zcfQ-iE-o5Fx=6BWvYss3X-Kr=-g=+=Q_h@mail.gmail.com>
On 08/27/2010 04:00 PM, Dhananjay Goel wrote:
> Yeah, I think so. I think this is basically the USB over IP interface
> which makes the impression of sharing and it even may be called
> sharing but one device is being still physically connected to one
> slot/device and not multiple at once.
>
> --Yes, exactly. It is just connected to one slot/device and not
> multiple but this device should be accessible to each virtual machine?
> As each virtual machine is sharing the same hardware. Please let me
> know if it makes sense.
>
> Thanks,
> Dhananjay
Basically that's right. It makes sense Dhananjay because this is the USB
over IP type of sharing. Imagine you have one device, let's say
hard-drive connected to the USB and there's some kind of protocol to
share it over the internet. It's more or less like let's say FTP server
with the exception that we don't access the FTP server application but
we access the USB hard-drive instead. It can accept all the command
using e.g. the HTTP protocol and the commands may be done simultaneously
when not conflicting with the other clients for which the perfect
example is the read-only access. Since it's not conflicting with any
other client every user/client could place a request on some file and
the file is being retrieved using the USB-over-IP protocol and the data
sent to the client that requested them. The virtual machines are sharing
the same hardware so that's why I used comparison to HTTP/FTP server and
it's clients. The logic is pretty similar AFAIK.
Michal
>
>
> On Fri, Aug 27, 2010 at 7:20 PM, Michal Novotny <minovotn@redhat.com
> <mailto:minovotn@redhat.com>> wrote:
>
> On 08/27/2010 03:34 PM, Pasi Kärkkäinen wrote:
>
> On Fri, Aug 27, 2010 at 06:59:55PM +0530, Dhananjay Goel wrote:
>
> I don't think USB protocol has been designed for *sharing*.
> I'm pretty certain only one computer/device/VM can use
> USB device at a
> time.
> --Please check:*[1]http://spice-space.org/*They're
> <http://spice-space.org/*They%27re> trying similar thing.
>
>
> I think SPICE protocol allows you to *transport* (aka connect)
> single
> USB device to single desktop OS. It's not USB sharing.
>
> It's basicly USB-over-IP.. replacing the physical USB cable
> with IP connection.
>
> -- Pasi
>
>
> Yeah, I think so. I think this is basically the USB over IP
> interface which makes the impression of sharing and it even may be
> called sharing but one device is being still physically connected
> to one slot/device and not multiple at once.
>
>
> Michal
>
> --
> Michal Novotny<minovotn@redhat.com <mailto:minovotn@redhat.com>>, RHCE
> Virtualization Team (xen userspace), Red Hat
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat
next prev parent reply other threads:[~2010-08-27 14:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=+Oa6dOcc0A9X37Bse0znrjT7AQ7Er7OQ5VVzq@mail.gmail.com>
2010-08-26 18:40 ` [Qemu-devel] Virtualization project idea Dhananjay Goel
2010-08-26 18:44 ` Dhananjay Goel
2010-08-26 19:56 ` Pasi Kärkkäinen
2010-08-26 22:58 ` James Harper
2010-08-27 8:07 ` Dhananjay Goel
2010-08-27 8:46 ` Pasi Kärkkäinen
2010-08-27 9:15 ` Dhananjay Goel
2010-08-27 9:19 ` Pasi Kärkkäinen
2010-08-27 9:20 ` David Markey
2010-08-27 9:23 ` Pasi Kärkkäinen
2010-08-27 9:25 ` Dhananjay Goel
2010-08-27 9:44 ` Keir Fraser
2010-08-27 9:48 ` Dhananjay Goel
2010-08-27 9:50 ` David Markey
2010-08-27 9:56 ` Dhananjay Goel
2010-08-27 9:57 ` Keir Fraser
2010-08-27 18:26 ` Gianni Tedesco
2010-08-27 9:23 ` Dhananjay Goel
2010-08-27 10:31 ` Marc - A. Dahlhaus
2010-08-27 10:57 ` Pasi Kärkkäinen
2010-08-27 11:26 ` Dhananjay Goel
2010-08-27 11:54 ` Pasi Kärkkäinen
2010-08-27 12:46 ` Dhananjay Goel
2010-08-27 12:53 ` Pasi Kärkkäinen
2010-08-27 13:03 ` Dhananjay Goel
2010-08-27 13:08 ` Pasi Kärkkäinen
2010-08-27 13:17 ` Michal Novotny
2010-08-27 13:30 ` Pasi Kärkkäinen
2010-08-27 13:35 ` Dhananjay Goel
2010-08-27 13:46 ` Pasi Kärkkäinen
2010-08-27 13:55 ` Dhananjay Goel
2010-08-27 14:09 ` Pasi Kärkkäinen
2010-08-27 13:47 ` Michal Novotny
2010-08-27 17:05 ` Pasi Kärkkäinen
2010-08-27 13:18 ` Christoph Egger
2010-08-27 13:22 ` Pasi Kärkkäinen
2010-08-27 13:26 ` Michal Novotny
2010-08-27 13:33 ` Pasi Kärkkäinen
2010-08-27 13:48 ` Michal Novotny
2010-08-27 13:29 ` Dhananjay Goel
2010-08-27 13:34 ` Pasi Kärkkäinen
2010-08-27 13:50 ` Michal Novotny
2010-08-27 14:00 ` Dhananjay Goel
2010-08-27 14:20 ` Michal Novotny [this message]
2010-08-27 16:58 ` Pasi Kärkkäinen
2010-08-27 15:12 ` Gianni Tedesco
2010-08-27 16:21 ` Konrad Rzeszutek Wilk
2010-08-27 16:51 ` [Qemu-devel] Re: [Xen-devel] " Stefano Stabellini
2010-08-27 16:51 ` Stefano Stabellini
2010-08-27 17:01 ` [Qemu-devel] Re: [Xen-devel] " David Markey
2010-08-27 17:01 ` David Markey
2010-08-27 17:06 ` [Qemu-devel] Re: [Xen-devel] " Pasi Kärkkäinen
2010-08-27 17:06 ` Pasi Kärkkäinen
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=4C77C9C5.1010307@redhat.com \
--to=minovotn@redhat.com \
--cc=dhananjaygoel123@gmail.com \
--cc=james.harper@bendigoit.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.