Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1382695

Summary: [RFE 7.4] support for virtio-vsock - glibc
Product: Red Hat Enterprise Linux 7 Reporter: Ademar Reis <areis>
Component: glibcAssignee: glibc team <glibc-bugzilla>
Status: CLOSED NOTABUG QA Contact: qe-baseos-tools-bugs
Severity: medium Docs Contact:
Priority: high    
Version: 7.3CC: ashankar, fweimer, hannsj_uhl, huding, john.spray, juzhang, knoel, lijin, lmiksik, mnewsome, mtessun, mzhan, pfrankli, qzhang, ssaha, stefanha, virt-bugs, virt-maint, xfu, yzimmerm
Target Milestone: rcKeywords: FutureFeature
Target Release: 7.4   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1291282 Environment:
Last Closed: 2017-01-27 14:11:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1291282    
Bug Blocks: 1291284, 1291286, 1291851, 1294879, 1294880, 1294884, 1299988, 1315822, 1359843, 1363787, 1378137, 1415819, 1518995, 1518996, 1518997    

Description Ademar Reis 2016-10-07 12:43:32 UTC 
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 +++
Comment 1 Carlos O'Donell 2016-10-07 14:28:20 UTC 
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.
Comment 2 Stefan Hajnoczi 2017-01-27 14:11:47 UTC 
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.