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.

Description of problem:
Start virtiofs service failed on guest.
F:\viofs\2k22\amd64>virtiofs.exe
The service 楖瑲佉䘭S has failed to start (Status=c000000e).


Version-Release number of selected component (if applicable):
qemu-kvm-6.1.0-3.el9.x86_64
5.14.0-3.el9.x86_64
virtio-win-prewhql-210

How reproducible:
100%

Steps to Reproduce:
1.boot up win2022 guest and install viofs driver(210 version)
2.start virtiofs service in guest
F:\viofs\2k22\amd64>virtiofs.exe
The service 楖瑲佉䘭S has failed to start (Status=c000000e).



Actual results:
Failed to start

Expected results:
Success to start virtiofs service

Additional info:
  1. virtiofsd log:
[root@dell-per440-06 home]#   /usr/libexec/virtiofsd --socket-path=/tmp/socket1 -o source=/home/test
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
virtio_loop: Entry
fv_queue_set_started: qidx=0 started=1
fv_queue_thread: Start for queue 0 kick_fd 8

Didn't reproduce on virtio-win-prewhql-209, so it's a regression

hit the same issue when run virtio-win-prewhql-0.1-211 acceptance test 

version:
kernel-4.18.0-345.1.el8.x86_64
qemu-kvm-6.1.0-1.module+el8.6.0+12721+8d053ff2.x86_64
seabios-bin-1.14.0-1.module+el8.6.0+12721+8d053ff2.noarch
virtio-win-prewhql-0.1-211 

guest:Win8.1-32/64,Win10-32/64.Win11,Win2012,Win12-r2,Win2016.Win2019,Win2022

hit the same issue when run virtio-win-prewhql-0.1-212 acceptance test 

version:
kernel-4.18.0-345.1.el8.x86_64
qemu-kvm-6.1.0-1.module+el8.6.0+12721+8d053ff2.x86_64
seabios-bin-1.14.0-1.module+el8.6.0+12721+8d053ff2.noarch
virtio-win-prewhql-0.1-212 

guest:Win8.1-32/64,Win10-32/64.Win11,Win2012,Win12-r2,Win2016.Win2019,Win2022

PR merged upstream: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/667

Test pass on virtio-win-prewhql-214.
Verify this bz.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: virtio-win), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3890