On Sat, Sep 16, 2017 at 08:55:21AM -0700, Chuck Lever wrote: > > > On Sep 15, 2017, at 9:42 AM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > > > > On Fri, Sep 15, 2017 at 06:59:45AM -0700, Chuck Lever wrote: > >> > >>> On Sep 15, 2017, at 6:31 AM, J . Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > >>> > >>> On Fri, Sep 15, 2017 at 02:12:24PM +0100, Stefan Hajnoczi wrote: > >>>> On Thu, Sep 14, 2017 at 01:37:30PM -0400, J . Bruce Fields wrote: > >>>>> On Thu, Sep 14, 2017 at 11:55:51AM -0400, Steve Dickson wrote: > >>>>>> On 09/14/2017 11:39 AM, Steve Dickson wrote: > >>>>>>> Hello > >>>>>>> > >>>>>>> On 09/13/2017 06:26 AM, Stefan Hajnoczi wrote: > >>>>>>>> v3: > >>>>>>>> * Documented vsock syntax in exports.man, nfs.man, and nfsd.man > >>>>>>>> * Added clientaddr autodetection in mount.nfs(8) > >>>>>>>> * Replaced #ifdefs with a single vsock.h header file > >>>>>>>> * Tested nfsd serving both IPv4 and vsock at the same time > >>>>>>> Just curious as to the status of the kernel patches... Are > >>>>>>> they slated for any particular release? > >>>>>> Maybe I should have read the thread before replying ;-) > >>>>>> > >>>>>> I now see the status of the patches... not good! 8-) > >>>>> > >>>>> To be specific, the code itself is probably fine, it's just that nobody > >>>>> on the NFS side seems convinced that NFS/VSOCK is necessary. > >>>> > >>>> Yes, the big question is whether the Linux NFS maintainers can see this > >>>> feature being merged. It allows host<->guest file sharing in a way that > >>>> management tools can automate. > >>>> > >>>> I have gotten feedback multiple times that NFS over TCP/IP is not an > >>>> option for management tools like libvirt to automate. > >>> > >>> We're having trouble understanding why this is. > >> > >> I'm also having trouble understanding why NFS is a better solution > >> in this case than a virtual disk, which does not require any net- > >> working to be configured. What exactly is expected to be shared > >> between the hypervisor and each guest? > > > > They have said before there are uses for storage that's actually shared. > > (And I assume it would be mainly shared between guests rather than > > between guest and hypervisor?) > > But this works today with IP-based networking. We certainly use > this kind of arrangement with OVM (Oracle's Xen-based hypervisor). > I agree NFS in the hypervisor is useful in interesting cases, but > I'm separating the need for a local NFS service with the need for > it to be zero-configuration. > > The other use case that's been presented for NFS/VSOCK is an NFS > share that contains configuration information for each guest (in > particular, network configuration information). This is the case > I refer to above when I ask whether this can be done with a > virtual disk. > > I don't see any need for concurrent access by the hypervisor and > guest, and one presumably should not share a guest's specific > configuration information with other guests. There would be no > sharing requirement, and therefore I would expect a virtual disk > filesystem would be adequate in this case and perhaps even > preferred, being more secure and less complex. There are 2 main use cases: 1. Easy file sharing between host & guest It's true that a disk image can be used but that's often inconvenient when the data comes in individual files. Making throwaway ISO or disk image from those files requires extra disk space, is slow, etc. From a user perspective it's much nicer to point to a directory and have it shared with the guest. 2. Using NFS over AF_VSOCK as an interface for a distributed file system like Ceph or Gluster. Hosting providers don't necessarily want to expose their distributed file system directly to the guest. An NFS frontend presents an NFS file system to the guest. The guest doesn't have access to the distributed file system configuration details or network access. The hosting provider can even switch backend file systems without requiring guest configuration changes. > >> I do understand the use cases for a full-featured NFS server in > >> the hypervisor, but not why it needs to be zero-config. > > > > "It" in that question refers to the client, not the server, right? > > The hypervisor gets a VSOCK address too, which makes it zero- > configuration for any access via VSOCK transports from its guests. > I probably don't understand your question. > > Note that an NFS server could also run in one of the guests, but > I assume that the VSOCK use cases are in particular about an NFS > service in the hypervisor that can be made available very early > in the life of a guest instance. I make that guess because all > the guests have the same VSOCK address (as I understand it), so > that would make it difficult to discover and access an NFS/VSOCK > service in another guest. Guest cannot communicate with each other. AF_VSOCK is host<->guest only. The host always uses the well-known CID (address) 2. Guests have host-wide unique addresses (from 3 onwards). Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
