-
Notifications
You must be signed in to change notification settings - Fork 510
Prevent error on windows virtiofs mount #1793
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
base: main
Are you sure you want to change the base?
Conversation
Dummy check if stating windows has a capability will not error out.
A docker image containing the code from this plugin to allow testing locally without installing If you need the image with the full dev toolchain, you can instead pull: ghcr.io/vagrant-libvirt/vagrant-libvirt:pr-1793 |
As a detail, the box I am using was build from the main branch of: https://github.com/ruzickap/ansible-role-virtio-win
|
* Add s3 plugin here instead of sed-ing during install. * Add log4r missing when building standalone.
* Redirect this branch to own fork
* Attempt adding Gemfile.lock
After installing WinFSP and the virtiofs driver in the provisioning phase, then configuring the service to autostart with
sc config VirtioFsSvc binPath="C:\Program Files\Virtio-Win\VioFS\virtiofs.exe" start=auto depend=VirtioFsDrv
... the virtiofs share gets mounted as a separate drive in Windows 10.Guide: https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/Virtiofs:-Shared-file-system#setup-with-installer
I have no experience writing vagrant plugins. In my fork I have just tried to implement a NOOP so that the libvirt plugin doesn't error out because of the missing guest capability. This works for me as
vagrant up
succeeds and the share works properly.Question for maintainers. Would this be ok to merge into main, to prevent the error? The capability obviously exists, but I do not know what would be acceptable for main.