Description of problem:
We now have virtio-vsock support in QEMU/KVM, which implements a host/guest communication device, allowing applications from guest and host to communicate without the need of a network. It implements the POSIX Sockets API and supports both SOCK_STREAM and SOCK_DGRAM. VSOCK itself has been available in the linux kernel since 3.9.
We're trying to push glibc patches upstream to add AF_VSOCK support to getnameinfo(3) and getaddrinfo(3): https://sourceware.org/ml/libc-alpha/2016-09/msg00580.html
For virtio-vsock support in QEMU/kernel, see bug 1291282 and bug 1291284.
The primary use-case for this feature is Virt-FS, where we export a NFS mount to the guest without needing to setup a TCP/IP network. For NFS BZs, see bug 1291286 and bug 1294880.
It's also going to be required by Ceph in OpenStack, see bug 1363787.
+++ This bug was initially created as a clone of Bug #1291282 +++
Just to be clear, these changes need to land upstream before they can be considered acceptable in RHEL7.
I encourage everyone to continue the upstream discussion to reach consensus on a solution.
I am not pursuing this further. After adding AF_VSOCK support to qemu-guest-agent, systemd, and nfs-utils without getaddrinfo(3) there is no immediate need for this change.