On Fri, Jun 30, 2017 at 11:01:13AM -0400, Steve Dickson wrote: > On 06/30/2017 09:21 AM, Stefan Hajnoczi wrote: > > Neither libtirpc nor getprotobyname(3) know about AF_VSOCK. For similar > > reasons as for "rdma"/"rmda6", translate "vsock" manually in getport.c. > > > > It is now possible to mount a file system from the host (hypervisor) > > 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. > So this is how vsocks are going to look... > There is not going to be a way to lookup an vsock address? > Since the format of the clientaddr parameter shouldn't > that be documented in the man page? AF_VSOCK does not have name resolution. The scope of the CID addresses is just the hypervisor that the VMs are running on. Inter-VM communication is not allowed. The virtualization software has the CIDs so there's not much use for name resolution. > I guess a general question, is this new mount type > documented anywhere? Thanks for pointing this out. I'll update the man pages in the next revision of this patch series.
Attachment:
signature.asc
Description: PGP signature
