WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Virtualization project idea

To: Dhananjay Goel <dhananjaygoel123@xxxxxxxxx>
Subject: Re: [Xen-devel] Virtualization project idea
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Fri, 27 Aug 2010 17:09:40 +0300
Cc: sourabh yerfule <sourabhfriend@xxxxxxxxx>, Michal Novotny <minovotn@xxxxxxxxxx>, James Harper <james.harper@xxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 27 Aug 2010 07:16:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTi=npHjx+y1QWeNv3XDtbkGQ3_EVzEJm2KoFbagz@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100827115449.GE2804@xxxxxxxxxxx> <AANLkTinUbCBwjJ17=8n9z8OwEUh8+oea_+-EYEVv1xA3@xxxxxxxxxxxxxx> <20100827125317.GF2804@xxxxxxxxxxx> <AANLkTikke8p3+m9C_npP87VVJA5czya2ie-xyFNC5pgx@xxxxxxxxxxxxxx> <20100827130847.GG2804@xxxxxxxxxxx> <4C77BAF3.2050609@xxxxxxxxxx> <20100827133042.GI2804@xxxxxxxxxxx> <AANLkTinVUBL=23t8Fu0E+uB9ub0NA0fcPof-wZygviBD@xxxxxxxxxxxxxx> <20100827134624.GL2804@xxxxxxxxxxx> <AANLkTi=npHjx+y1QWeNv3XDtbkGQ3_EVzEJm2KoFbagz@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Aug 27, 2010 at 07:25:39PM +0530, Dhananjay Goel wrote:
>    Yes, you can build some filesystem protocol and share ANY filesystem,
>    be it USB, SATA, SAS, RAID, whatnot.
> 
>    If it's filesystem protocol it doesn't matter at all if it's USB or not.
>    --But here we're sharing filesystem and not USB itself. Suppose we connect
>    internet through USB device, we can share data but not internet
>    connection, right?*
>    A few more questions:
>    1)*whether to use NFS and create plugins for different Oss. By plugin I
>    mean we'll be writing some code which will support windows sharing, some
>    code for linux sharing, etc
>    2)*if not NFS then should we write some module to manage contexts and
>    switch between host and guest. This will involve some device driver coding
>    3)*using NFS I guess we can't implement the USB internet . How to proceed
>    on that?
>

Uhm, this is a bit confusing now..
If you connect to Internet over an USB device, then you're using *IP* 
connection there.

You can share IP connection using the networking stack! Configure NAT, routing, 
bridging,
whatever you need. This is how it's done today with Xen and other 
virtualization solutions.
No need to know anything about USB to do that.

You need to start thinking about *functionality*, not about the fact if it's 
USB device or not.

USB device can be used only by *one* computer/host/VM. Then you can share it 
*from* 
that computer/host/VM using other protocols/means.

-- Pasi

>    Thanks,
>    Dhananjay
> 
>    On Fri, Aug 27, 2010 at 7:16 PM, Pasi K*rkk*inen <[1]pasik@xxxxxx> wrote:
> 
>      On Fri, Aug 27, 2010 at 07:05:11PM +0530, Dhananjay Goel wrote:
>      > * *If you don't want to do it over-the-network, but somehow 'through'
>      the
>      > * *hypervisor,
>      > * *then you'd need to build some kind of special filesystem protocol
>      that is
>      > * *able
>      > * *to do the client-server communication over the hypervisor specific
>      paths
>      > * *(xenbus etc).
>      > * *And have drivers for it in the hypervisor-host, and in the VMs.
>      > * *--So, is it possible to build a filesystem protocol to share USB
>      devices?
>      > * *Is my project feasible?
>      >
> 
>      Yes, you can build some filesystem protocol and share ANY filesystem,
>      be it USB, SATA, SAS, RAID, whatnot.
> 
>      If it's filesystem protocol it doesn't matter at all if it's USB or not.
> 
>      -- Pasi
> 
>      > * *Thanks,
>      > * *Dhananjay
>      >
>      > * *On Fri, Aug 27, 2010 at 7:00 PM, Pasi K*rkk*inen
>      <[1][2]pasik@xxxxxx> wrote:
>      >
>      > * * *On Fri, Aug 27, 2010 at 03:17:39PM +0200, Michal Novotny wrote:
>      > * * *> On 08/27/2010 03:08 PM, Pasi K*rkk*inen wrote:
>      > * * *>> On Fri, Aug 27, 2010 at 06:33:35PM +0530, Dhananjay Goel
>      wrote:
>      > * * *>>
>      > * * *>>> * * Yes, exactly. So, we wanted to know if it is possible to
>      *share
>      > * * *USB*
>      > * * *>>> * * across VMs.
>      > * * *>>>
>      > * * *>>>
>      > * * *>> 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.
>      > * * *>>
>      > * * *>> -- Pasi
>      > * * *>>
>      > * * *>>
>      > * * *>
>      > * * *> Pasi, I agree. I think the think here is that Dhananjay
>      confused the
>      > * * *USB
>      > * * *> device sharing with the file system sharing. I guess the USB
>      protocol
>      > * * *> was not designed for sharing nevertheless sharing the
>      filesystem on a
>      > * * *> USB stick is a completely different think.
>      > * * *>
>      > * * *> Dhananajay, you need to plug in the USB stick onto one computer
>      (and
>      > * * *> it's impossible to plug it into multiple computer at one time,
>      of
>      > * * *> course) and then setup the sharing. Everybody here is talking
>      about
>      > * * *the
>      > * * *> hardware abstraction and virtualization and what you wrote is a
>      > * * *> completely different thing - it's software-related and this has
>      > * * *nothing
>      > * * *> to do with the hardware emulation/abstraction what-so-ever.
>      > * * *>
>      > * * *> Considering the NFS and all the sharing protocols there was
>      something
>      > * * *> why it doesn't corrupt the data. I'm no expert on this subject
>      but I
>      > * * *> think this is because they run in the server-client mode. All
>      the
>      > * * *> clients are talking to the server and the server itself is one
>      > * * *computer
>      > * * *> that's having the just one operating system working with this
>      > * * *particular
>      > * * *> device - no matter what the underlaying device is - it may be
>      > * * *everything
>      > * * *> - USB stick, IDE/SCSI/SAS drive or just a relay workstation to
>      save
>      > * * *all
>      > * * *> the data into one remote media (e.g. for replication). What I
>      mean is
>      > * * *> that the basic thing is that it's running on only one operating
>      system
>      > * * *> (because of it's connected to this one machine *only*) so it
>      takes
>      > * * *care
>      > * * *> of everything and it's aware of the write-cache and data
>      operations
>      > * * *> being done to this media.
>      > * * *>
>      >
>      > * * *Yep.
>      >
>      > * * *If you want to share files from the hypervisor-host (from USB
>      stick or
>      > * * *from actual disk)
>      > * * *to the VMs you *can* do it today over-the-network
>      (nfs,cifs,webdav,ftp)
>      > * * *using the standard
>      > * * *client-server tools that have been used for over 20 years.
>      >
>      > * * *If you don't want to do it over-the-network, but somehow
>      'through' the
>      > * * *hypervisor,
>      > * * *then you'd need to build some kind of special filesystem protocol
>      that
>      > * * *is able
>      > * * *to do the client-server communication over the hypervisor
>      specific paths
>      > * * *(xenbus etc).
>      > * * *And have drivers for it in the hypervisor-host, and in the VMs.
>      > * * *-- Pasi
>      >
>      > References
>      >
>      > * *Visible links
>      > * *1. mailto:[3]pasik@xxxxxx
> 
> References
> 
>    Visible links
>    1. mailto:pasik@xxxxxx
>    2. mailto:pasik@xxxxxx
>    3. mailto:pasik@xxxxxx

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel