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 2144769 - [virtio-win][virtiofs] Start virtiofs service failed on ws2012 and ws2012r2 with a newer WinFSP(Error 577)
Summary: [virtio-win][virtiofs] Start virtiofs service failed on ws2012 and ws2012r2 w...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.2
Hardware: x86_64
OS: Windows
low
low
Target Milestone: rc
: ---
Assignee: Meirav Dean
QA Contact: xiagao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-22 09:32 UTC by xiagao
Modified: 2022-12-26 07:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-26 07:10:59 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-140138 0 None None None 2022-11-22 09:40:31 UTC

Description xiagao 2022-11-22 09:32:28 UTC
Description of problem:
Start virtiofs service failed on ws2012 and ws2012r2 with a newer WinFSP software, it shows "Error 577: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged...."

Failed on WinFSP 2022.2 Beta2
works on WinFsp 1.9.21096

Version-Release number of selected component (if applicable):
virtio-win-prewhql-0.1-229
qemu-kvm-7.1.0-5.el9.x86_64
kernel-5.14.0-194.el9.x86_64
WinFSP 2022.2 Beta2

How reproducible:
100%

Steps to Reproduce:
1.start virtiofsd
/usr/libexec/virtiofsd --socket-path=/var/tmp/avocado_yv7atpg8/avocado-vt-vm1-fs-virtiofsd.sock -o source=/root/avocado/data/avocado-vt/virtio_fs_test/ -o cache=always

2.start win2012r2 guest
[stdlog]     -chardev socket,id=char_virtiofs_fs,path=/var/tmp/avocado_yv7atpg8/avocado-vt-vm1-fs-virtiofsd.sock \
[stdlog]     -device pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \
[stdlog]     -device vhost-user-fs-pci,id=vufs_virtiofs_fs,chardev=char_virtiofs_fs,tag=myfs,queue-size=1024,bus=pcie-root-port-3,addr=0x0 \

3. install WinFSP 2022.2 Beta2

4. create virtiofs service in guest
sc create VirtioFsSvc binpath=C:\virtiofs.exe start=auto depend="WinFsp.Launcher/VirtioFsDrv" DisplayName="Virtio FS Service"

5. start virtiofs service in service manager


Actual results:
Failed to start, it shows "Error 577: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged...."



Expected results:
Can start.

Additional info:
1. Failed on WinFSP 2022.2 Beta2
   works on WinFsp 1.9.21096
2. Event log when fail to start vfs service.

+ System 

  - Provider 

   [ Name]  Service Control Manager 
   [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4} 
   [ EventSourceName]  Service Control Manager 
 
  - EventID 7000 

   [ Qualifiers]  49152 
 
   Version 0 
 
   Level 2 
 
   Task 0 
 
   Opcode 0 
 
   Keywords 0x8080000000000000 
 
  - TimeCreated 

   [ SystemTime]  2022-11-21T14:42:22.962910600Z 
 
   EventRecordID 1059 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  888 
   [ ThreadID]  2448 
 
   Channel System 
 
   Computer WIN-0B1NOAFCMG5 
 
   Security 
 

EventData 
  param1 WinFsp 
  param2 %%577 
   570069006E004600730070000000 

--------------------------------------------------------------------------------

Binary data:

In Words

0000: 00690057 0046006E 00700073 0000 

In Bytes

0000: 57 00 69 00 6E 00 46 00   W.i.n.F.
0008: 73 00 70 00 00 00         s.p...

Comment 4 Viktor Prutyanov 2022-12-24 23:23:40 UTC
Hi,

I've tried last available version - WinFsp 2022.2 Update1 (1.12.22339) from MSI package - https://github.com/winfsp/winfsp/releases/download/v1.12.22339/winfsp-1.12.22339.msi
The guest OS is Windows Server 2012 R2 Standard Build 9600.

Running virtiofs.exe from console or as a service works OK.
Maybe your issue is caused by Beta version of WinFsp?

Comment 5 xiagao 2022-12-26 07:10:59 UTC
(In reply to Viktor Prutyanov from comment #4)
> Hi,
> 
> I've tried last available version - WinFsp 2022.2 Update1 (1.12.22339) from
> MSI package -
> https://github.com/winfsp/winfsp/releases/download/v1.12.22339/winfsp-1.12.
> 22339.msi
> The guest OS is Windows Server 2012 R2 Standard Build 9600.
> 
> Running virtiofs.exe from console or as a service works OK.
> Maybe your issue is caused by Beta version of WinFsp?

Download the winfsp pkg provided above and try it on win2012.r2 guest, everything works. If changing it back to the Beta version, it won't work.

Anyway, the latest winfsp works on win2012.r2, I will update it in our test.

Thanks.


Note You need to log in before you can comment on or make changes to this bug.