-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
virtiofs ignoring CLI arguments when created as a service #1083
Comments
@kantlivelong Hi, |
This works for a single virtiofs tag but not multiple. The documentation also mentions using WinFSP for multiple but that is not persistent from what I can tell. |
Hi @kantlivelong, here is my steps with multiple virtiofs, it works from my side.
Btw, I refer to Multiple virtiofs instances setup in the wiki Hope this is helpful. |
I did see that part of the documentation and gave it a try before opening this ticket. While it did work I found that it did not persist on reboot. Is the expectation that a bat be created and run via task scheduler on boot? |
Hi @YanVugenfirer , do we have any plan regarding @kantlivelong 's situation? And for multiple shared dir, I don't think it works with "sc create VirtioFsSvc-data binPath=""C:\Program Files\Virtio-Win\VioFS\virtiofs.exe" -t data -m D:" start=auto depend=VirtioFsDrv", what's your opinion? |
Currently for the multiple mounts, a WinFSP launcher should be used. So, yes - the solution is batch files on boot to configure the mounts. We still need to fix an issue of mismatch of the configuration in the registry and in CLI. @xiagao I suggest opening Jira for this. |
Describe the bug
When creating an additional service
VirtioFsSvc-TAG
the CLI arguments appear to be ignored.To Reproduce
VirtioFsSvc
serviceExpected behavior
Tag
data
should be mounted toD:
but instead the reg values are being used.Screenshots
If applicable, add screenshots to help explain your problem.
Host:
Ubuntu 24.04.4
6.5.0-26-generic
QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.17)
8.0.0-1ubuntu7.8
VM:
Windows Server 2022
virtiofs
0.1.240
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: