From: Stefan Hajnoczi <stefanha@redhat.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/4] nfs-utils mount: add AF_VSOCK support
Date: Wed, 4 Jan 2017 13:31:21 +0000 [thread overview]
Message-ID: <20170104133121.GA5081@stefanha-x1.localdomain> (raw)
In-Reply-To: <5e994b44-8b88-62f8-3c09-6d8cb459e303@RedHat.com>
[-- Attachment #1: Type: text/plain, Size: 2416 bytes --]
On Tue, Jan 03, 2017 at 11:37:58AM -0500, Steve Dickson wrote:
>
>
> On 10/07/2016 06:01 AM, Stefan Hajnoczi wrote:
> > The AF_VSOCK address family allows virtual machines to communicate with the
> > hypervisor using a zero-configuration transport. Both KVM and VMware
> > hypervisors support AF_VSOCK and it was introduced in Linux 3.9.
> >
> > This patch series adds AF_VSOCK support to mount.nfs(8) and works together with
> > the kernel NFS client patches that I am also posting to
> > linux-nfs@vger.kernel.org.
> >
> > NFS over AF_VSOCK is useful for file system sharing between a virtual machine
> > and the host. Due to the zero-configuration nature of AF_VSOCK this is more
> > transparent to the user and more robust than asking the user to set up NFS over
> > TCP/IP.
> >
> > A file system from the host (hypervisor) can be mounted inside a virtual
> > machine over AF_VSOCK like this:
> >
> > (guest)# mount.nfs 2:/export /mnt -v -o clientaddr=3,proto=vsock
> >
> > The VM's cid (address) is 3 and the hypervisor is 2.
> >
> > For testing it's easiest to tunnel AF_VSOCK to the AF_INET nfsd on the host.
> > The following utility can do this:
> > https://github.com/stefanha/linux/blob/vsock-extras/nc-vsock.c
> >
> > (host)# nc-vsock -l 2049 -t 127.0.0.1 2049
> >
> > I will post nfsd patches for both the kernel and nfs-utils once they are
> > complete.
> >
> > Alternatively you can use nfs-ganesha's AF_VSOCK support to run a native
> > AF_VSOCK server.
> >
> > Note that this patch series relies on the AF_VSOCK getaddrinfo(3) support I
> > recently posted to glibc:
> > https://patchwork.ozlabs.org/patch/676589/
> >
> > Stefan Hajnoczi (4):
> > mount: don't use IPPROTO_UDP for address resolution
> > mount: present AF_VSOCK addresses
> > mount: accept AF_VSOCK in nfs_verify_family()
> > getport: recognize "vsock" netid
> >
> > support/nfs/getport.c | 16 ++++++++++++----
> > utils/mount/network.c | 10 +++++++++-
> > utils/mount/stropts.c | 4 +---
> > 3 files changed, 22 insertions(+), 8 deletions(-)
> >
> My apologies... I did lose track of these...
>
> Where the kernel patches for the AF_VSOCK support
> accepted??
No, they haven't been merged because the discussion was slow (largely my
fault). I'll send out a new round of kernel and nfs-utils patches with
the latest code soon.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-01-04 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 10:01 [PATCH 0/4] nfs-utils mount: add AF_VSOCK support Stefan Hajnoczi
2016-10-07 10:01 ` [PATCH 1/4] mount: don't use IPPROTO_UDP for address resolution Stefan Hajnoczi
2017-05-17 19:39 ` Jeff Layton
2016-10-07 10:01 ` [PATCH 2/4] mount: present AF_VSOCK addresses Stefan Hajnoczi
2016-10-07 10:01 ` [PATCH 3/4] mount: accept AF_VSOCK in nfs_verify_family() Stefan Hajnoczi
2016-10-07 10:01 ` [PATCH 4/4] getport: recognize "vsock" netid Stefan Hajnoczi
2017-01-03 16:37 ` [PATCH 0/4] nfs-utils mount: add AF_VSOCK support Steve Dickson
2017-01-04 13:31 ` Stefan Hajnoczi [this message]
2017-05-17 16:51 ` Jeff Layton
2017-05-18 12:48 ` Stefan Hajnoczi
2017-05-18 14:07 ` Jeff Layton
2017-05-22 12:12 ` Stefan Hajnoczi
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=20170104133121.GA5081@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.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).