Bug 2007601

Summary: [virtio-win] start virtiofs.exe failed with virtio-win-prewhql-210 on windows guest
Product: Red Hat Enterprise Linux 9 Reporter: xiagao
Component: virtio-winAssignee: Yvugenfi <yvugenfi>
virtio-win sub component: virtio-win-prewhql QA Contact: xiagao
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: lkotek, mdean, pvlasin, xfu, yfu
Version: 9.0Keywords: Regression, TestBlocker
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 15:35:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description xiagao 2021-09-24 11:04:10 UTC 
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
Comment 1 xiagao 2021-09-24 11:13:08 UTC 
Didn't reproduce on virtio-win-prewhql-209, so it's a regression
Comment 2 ChenNana 2021-10-09 08:57:58 UTC 
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
Comment 5 ChenNana 2021-10-14 03:51:26 UTC 
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
Comment 8 Yvugenfi@redhat.com 2021-10-26 06:09:11 UTC 
PR merged upstream: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/667
Comment 11 xiagao 2021-11-02 06:39:47 UTC 
Test pass on virtio-win-prewhql-214.
Verify this bz.
Comment 15 errata-xmlrpc 2022-05-17 15:35:27 UTC 
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