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 1077172

Summary: Disable addhw filesystem passthrough for RHEL7 qemu
Product: Red Hat Enterprise Linux 7 Reporter: Cole Robinson <crobinso>
Component: virt-managerAssignee: Giuseppe Scrivano <gscrivan>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: dyuan, gscrivan, lcui, mzhan, rjones, tzheng
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-manager-0.10.0-19.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 11:16:13 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:

Description Cole Robinson 2014-03-17 11:53:36 UTC
RHEL7 qemu-kvm compiled out virtio-9pfs, so we should disable it if using RHEL7 qemu-kvm. dgilbert hit something similar last week, and we already have a user mentioning it on virt@fedora so it will likely be a common complaint:

https://lists.fedoraproject.org/pipermail/virt/2014-March/004003.html

Should be as simple as:

diff --git a/virtManager/addhardware.py b/virtManager/addhardware.py
index 1e91505..4bd776c 100644
--- a/virtManager/addhardware.py
+++ b/virtManager/addhardware.py
@@ -370,7 +370,8 @@ class vmmAddHardware(vmmGObjectUI):
                       _("Not supported for this guest type."))
         add_hw_option("Filesystem", Gtk.STOCK_DIRECTORY, PAGE_FILESYSTEM,
                       self.conn.check_support(
-                        self.conn.SUPPORT_CONN_FILESYSTEM),
+                        self.conn.SUPPORT_CONN_FILESYSTEM) and
+                      not self.vm.stable_defaults(),
                       _("Not supported for this hypervisor/libvirt "
                         "combination."))
         add_hw_option("Smartcard", "device_serial", PAGE_SMARTCARD,



But untested on RHEL

Comment 4 tingting zheng 2014-03-24 05:39:37 UTC
Tested with:
virt-manager-0.10.0-19.el7.noarch

Steps:
1.Launch virt-manager,open a guest.
2.Add hardware->"Filesystem",there is error message showed:"Not supported for this hypervisor/libvirt combination".

Refer to the above comments,move the bug to VERIFIED.

Comment 5 Ludek Smid 2014-06-13 11:16:13 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.