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.
DescriptionKaterina Koukiou
2021-06-01 12:52:54 UTC
Description of problem:
I have a VM with file backed shared memory and a virtiofs. Starting the VM fails with:
operation failed: Unable to find a satisfying virtiofsd
Version-Release number of selected component (if applicable):
qemu-kvm-common-6.0.0-1.el9.x86_64
libvirt-daemon-7.0.0-4.el9.x86_64
How reproducible:
Always
Steps to Reproduce:
1.
Add:
<memoryBacking>
<access mode='shared'/>
</memoryBacking>
<filesystem type='mount' accessmode='passthrough'>
<driver type='virtiofs'/>
<source dir='/tmp/dir1/'/>
<target dir='dir1'/>
</filesystem>
2. Attempt to start the guest
Actual results:
VM fails to start:
operation failed: Unable to find a satisfying virtiofsd
Additional info:
/usr/libexec/virtiofsd file exists
Libvirt looks for virtiofsd JSON description file in the following paths:
/usr/share/qemu/vhost-user/
/etc/qemu/vhost-user/
~/.config/qemu/vhost-user/
which is true for upstream QEMU or for example the one shipped in Fedora but in RHEL the files installed by package are in different directory:
/usr/share/qemu-kvm/vhost-user/
and that results in the error mentioned in BZ description.
Since these files are similar to UEFI firmware JSON description which are in RHEL shipped in the same directory as in upstream (/usr/share/qemu/firmware) I think we should do the same for vhost-user JSON description files.
Updating ownership to match the similar (but not cloned from) RHEL-AV bug 1804196.
If this is the same problem, then once that bug is merged/built - update the Dev Whiteboard w/ the downstream build reference and move this to POST to be merged into 9-Beta
Test the following pkg.
qemu-kvm-6.0.0-11.el9.x86_64
qemu-virtiofsd-6.0.0-11.el9.x86_64
# rpm -ql qemu-virtiofsd-6.0.0-11.el9.x86_64
/usr/lib/.build-id
/usr/lib/.build-id/95
/usr/lib/.build-id/95/05dd2ec972b5979b400409575cba2d92cb6d1d
/usr/libexec/virtiofsd
/usr/share/man/man1/virtiofsd.1.gz
/usr/share/qemu/vhost-user/50-qemu-virtiofsd.json
virtiofsd JSON description file is shipped in /usr/share/qemu/vhost-user/.
Verify this bz.
Description of problem: I have a VM with file backed shared memory and a virtiofs. Starting the VM fails with: operation failed: Unable to find a satisfying virtiofsd Version-Release number of selected component (if applicable): qemu-kvm-common-6.0.0-1.el9.x86_64 libvirt-daemon-7.0.0-4.el9.x86_64 How reproducible: Always Steps to Reproduce: 1. Add: <memoryBacking> <access mode='shared'/> </memoryBacking> <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs'/> <source dir='/tmp/dir1/'/> <target dir='dir1'/> </filesystem> 2. Attempt to start the guest Actual results: VM fails to start: operation failed: Unable to find a satisfying virtiofsd Additional info: /usr/libexec/virtiofsd file exists