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.
Once we have support for virtio-sock everywhere (QEMU, Kernel and NFS), libvirt will have to provide some mechanism for a Virt-FS feature, where a folder gets shared between host and guest.
+++ This bug was initially created as a clone of Bug #1294879 +++
We'we working on virtio-vsock in QEMU/KVM, which implements a host/guest communication device, allowing applications from both sides to communicate without the need of a network. It implements the POSIX Sockets API and supports both SOCK_STREAM and SOCK_DGRAM.
For virtio-vsock support in QEMU/kernel, see bug 1291282 and bug 1291284.
Once virtio-vsock is implemented, we want NFS (both server and client) to support it so that we can use it to share directories between the host and the guest, a feature we call "Virt-FS".
(In reply to IBM Bug Proxy from comment #4)
> ------- Comment From lagarcia.com 2017-06-19 15:17 EDT-------
> Is this on track for RHEL 7.4?
Unfortunately not. We're still working on upstream support for virtio-vsock in NFS and the complete feature has been deferred to a future release of RHEL or layered products.
(In reply to IBM Bug Proxy from comment #11)
> ------- Comment From lagarcia.com 2018-03-23 10:20 EDT-------
> Ademar,
>
> Is this on track for RHEL 7.5?
Unfortunately not. We couldn't get upstream NFS to accept vsock support yet, so this is still in progress. We had to submit a IETF RFC to get it accepted as a standard and that process takes time. Even RHEL-7.6 is a stretch target.
Will not be implemented in RHEL-7.
For sometime in RHEL-8, we're planning a different approach, using virtio-fs. This is being tracked via Bug 1519458 and Bug 1519459.
------- Comment From KURZGREG.com 2018-12-04 02:56 EDT-------
(In reply to comment #16)
> Will not be implemented in RHEL-7.
> For sometime in RHEL-8, we're planning a different approach, using
> virtio-fs. This is being tracked via Bug 1519458 and Bug 1519459.
Access to these BZs is denied, and they don't seem to have been mirrored to IBM's BZ.
Please provide access. My login in RH's BZ is gkurz.ibm.com.
(In reply to Ján Tomko from comment #15)
> I made bug 1519459 public since it does not contain any different
> information than this one.
Ditto for Bug 1519458.