Bug 2084421

Summary: libvirt windows 10 guest libvirt.libvirtError: operation failed: Unable to find a satisfying virtiofsd
Product: [Fedora] Fedora Reporter: tim richardson <tim>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 36CC: agedosier, berrange, clalancette, crobinso, jforbes, laine, libvirt-maint, tim, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 18:12:22 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 tim richardson 2022-05-12 05:29:29 UTC
Description of problem:
When adding a filesystem device via virtual machine manager (gui) of type virtiofs,
the VM will not start. The error is:
Error starting domain: operation failed: Unable to find a satisfying virtiofsd.

Under details: 

Error starting domain: operation failed: Unable to find a satisfying virtiofsd

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1384, in startup
    self._backend.create()
  File "/usr/lib64/python3.10/site-packages/libvirt.py", line 1353, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: operation failed: Unable to find a satisfying virtiofsd


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

virtual machine manager 4.0.0
Fedora 36 in wayland session
intel hardware (tigerlake)
selinux is in permissive mode

How reproducible:
A win 10 VM. Add virtiofs Filesystem with driver virtiofs



Actual results:
start up error

Expected results:


Additional info:
I also can not properly install the driver in Windows. I am following instructions and have installed the fuse driver (winfsp). The next step is to download an ISO with the driver code and install the vitio hardware mass storage device. But I do not see a mass storage device.

Comment 1 tim richardson 2022-05-12 05:34:42 UTC
Note: the package qemu-virtiofsd-2 needed to be installed. Perhaps this bug is simply a missing dependency somewhere in packaging. 
I only started using qemu/virtual manager very recently, I am a new user.

Comment 2 Cole Robinson 2022-05-17 18:12:22 UTC

*** This bug has been marked as a duplicate of bug 2083155 ***