Bug 2042247
| Summary: | [virtio-win][virtiofs] share more than one fs with virtio-fs for windiows guest | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | xiagao |
| Component: | virtio-win | Assignee: | Virtualization Maintenance <virt-maint> |
| virtio-win sub component: | virtio-win-prewhql | QA Contact: | xiagao |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | qizhu, vrozenfe, yvugenfi |
| Version: | 9.0 | Keywords: | Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| 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: | 2023-05-09 07:55:10 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
2022-01-19 06:07:22 UTC
Upstream PR to add initial support of multiple mounts: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/804 How to test: start "" virtiofs.exe -d -1 -D C:\viofs_debug0.txt -m Y: -t mount0 start "" virtiofs.exe -d -1 -D C:\viofs_debug1.txt -m Z: -t mount1 (or any other way to run several virtiofs.exe with different tags and mount points) please check with the drivers from build 223 https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=2109262 Hi Xiaoling, is the problem reproduced without '-t'? (In reply to Viktor Prutyanov from comment #5) > Hi Xiaoling, > > is the problem reproduced without '-t'? yes, it still failed without '-m x: -t myfs1' Could you please share security setting for the mounted drive in the guest? Such as: Right Click to Drive > Properties > Security Right Click to Drive > Properties > Security > Advanced Right Click to Drive > Properties > Security > Advanced > Edit (for each entry in Permissions) > Show Advanced permissions PowerShell: Get-Acl | fl CMD: dir /q And also host permissions for shared folder, please Hi Xiaoling, Thank you for providing the information. Could you please also share permissions for the shared folder itself (/home/test in your case)? For example, ls -la /home/test the fix included in build 226 https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=2176313 Manual how to setup multiple instances of VirtIO-FS: https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/VirtIO-FS:-Shared-file-system#multiple-virtio-fs-instances Try build 226. Can't access the shared volume in guest(attachment), so reassign back. Seems the same reason with https://bugzilla.redhat.com/show_bug.cgi?id=2112559#c10 New build should include the fix: virtio-win-prewhql-0.1-227 Test on virtio-win-prewhql-0.1-227, the driver letter name can't be changed when starting it with a service. Register virtiofs service cmd: sc create VirtioFsSvc binpath="c:\virtiofs.exe -m O: -t myfs" start=auto depend="WinFsp.Launcher/VirtioFsDrv" DisplayName="Virtio FS Service" Result: It shows "Z:" in computer manager. Hi Windows service can't accept command-line arguments. To specify mount point for VirtIO-FS Windows service use registry: https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/VirtIO-FS:-Shared-file-system#options Or use WinFsp's launchctl to run VirtIO-FS: https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/VirtIO-FS:-Shared-file-system#multiple-virtio-fs-instances (In reply to Viktor Prutyanov from comment #18) > Hi > Windows service can't accept command-line arguments. > To specify mount point for VirtIO-FS Windows service use registry: > https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/VirtIO-FS:- > Shared-file-system#options Hi Viktor, I have two mount points, how to modify both of them with registry. The first one. reg add HKLM\Software\VirtIO-FS /v MountPoint /d A: /t REG_SZ Then how to set another? Thanks. > Or use WinFsp's launchctl to run VirtIO-FS: > https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/VirtIO-FS:- > Shared-file-system#multiple-virtio-fs-instances Hi Xiaoling, 1) With WinFSP.Launcher you can run 1, 2 or more instances of VirtIO-FS. In this case '-t' can be used to specify tag. 2) A Windows service can be run only once, so the only one VirtIO-FS instance can be run by the service and no tag is required (if VirtIO-FS device is present it will be mounted regardless of tag). At the moment, both variants are supported, but we're discussing with Yan about leaving only WinFSP.Launcher way. (In reply to Viktor Prutyanov from comment #23) > Hi Xiaoling, > > 1) With WinFSP.Launcher you can run 1, 2 or more instances of VirtIO-FS. In > this case '-t' can be used to specify tag. OK, thanks for your explanation. > 2) A Windows service can be run only once, so the only one VirtIO-FS > instance can be run by the service and no tag is required (if VirtIO-FS > device is present it will be mounted regardless of tag). I guess it will mount the first VirtIO-FS device if there is more than one. > > At the moment, both variants are supported, but we're discussing with Yan > about leaving only WinFSP.Launcher way. Yeah, I also agree with one way to start the shared volume, it's more simple and easy to manage, in case people need to keep in mind the usage of two ways. So for this bug, I think it can be verified. It works with WinFSP.Launcher way. 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 (virtio-win bug fix and enhancement update), 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-2023:2451 |