RE: [Xen-devel] iscsi

["Williamson, Mark A" <mark.a.williamson@xxxxxxxxx>]

If you wanted to get something up and running straight away, you might
also want to look at unfsd (runs in user space, so can re-export the
LUNs you import with iSCSI - I don't think kernel NFSd will).

To ease the pain of using NFS to manage multiple machines, you could try
ClusterNFS (an enhancement of unfsd to make it easier to manage clusters
- may be useful for you - this was mentioned by Bin Ren in an earlier
thread).  Also, the user level copy-on-write nfsd (mentioned by Ian
Pratt in another thread) might be good although I don't know who's doing
that or when it'll be ready...

Mark

> -----Original Message-----
> From: Kip Macy [mailto:kmacy@xxxxxxxxxxx] 
> Sent: 20 January 2004 20:03
> To: Williamson, Mark A
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-devel] iscsi 
> 
> 
> >
> > To re-export iSCSI drives from dom0, I think you'd 
> currently need to use
> > NFS or something similar - to re-export them appearing as 
> "just another
> > VBD" to the guest would require extra code.
> 
> And extra layers + latency etc.
> 
> 
> >
> > Is this relevant or do I have the wrong end of the stick?
> 
> What you're saying sounds exactly right. Plus we can't stick a SW
> initiator in Xen without a TCP stack. My only hope would be a HW
> initiator. How annoying. I wonder how much work it would be to
> support what I'm thinking about? Managing NFS root for n virtual
> machines is much more annoying to manage. It would also make this
> a much harder sell internally.
> 
>                       -Kip
> 
> 
> 


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel