Bug 1379389

Summary: Filesystem passthrough "virtio-9pfs" support in KVM is missing in RHEL7
Product: Red Hat Enterprise Linux 7 Reporter: John L Magee <jlmagee>
Component: virt-managerAssignee: Pavel Hrdina <phrdina>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: jsuchane, juzhou, mxie, mzhan, tzheng, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 12:48:03 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:
Bug Depends On:    
Bug Blocks: 1401400    

Description John L Magee 2016-09-26 14:43:26 UTC
Description of problem:
Filesystem passthrough "virtio-9pfs" support in KVM is not implemented in RHEL7 

Version-Release number of selected component (if applicable):
7+

How reproducible:
NA

Steps to Reproduce:
1. NA
2.
3.

Actual results:
NA

Expected results:
NA

Additional info:
See https://access.redhat.com/discussions/1119043

Virt-Manager and probably most of libvirt still support device definition with no warning. There is no mention of this at libvirt.org.  the user finds out only after configuring a filesystem and then getting a "mount: unknown filesystem type '9p'" in the guest and undertaking research.

This may be old news but it is frustrating.

Comment 3 Pavel Hrdina 2017-01-17 12:48:03 UTC
This is not a bug, in RHEL-7 the filesystem passthrough was disabled because 9p is not reliable.

You can find more information in the discussion that you've provided as additional info.  Virt-manager in RHEL-7 correctly prints message "Not supported for this hypervisor/libvirt combination." if you try to add a new filesystem device.

There was a bug to disable 9p in RHEL-7 bug 1077172.