-
Notifications
You must be signed in to change notification settings - Fork 385
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
how to use virtiofs in Windows 10 guest? #473
Comments
where did you get this driver? it's not included yet. |
Assuming that qemu and virtiofsd are set and running on the host and you know how to compile the project for Windows you need to do the following: Install WinFsp, install the virtiofs Windows driver and then run the virtiofs service. |
I'm getting this with service After adding it services via sc.exe when staring manually I;m getting " the handle is invalid" |
ok i managed to compile viofs.sys driver. i added the following line to my vm: |
When you run virtiofs.exe from command line, was it in an Administrator console (Run as...)? |
Virtfs and virtio-fs are two different implementations of the shared files feature (PCI devices and protocols).
Where did you saw this error message? On Windows?
I submitted a patch which mount the shared folder as a disk drive (and remove the network option for now). |
Yes, tried it via admin console and later via services panel after registering it. Same issue |
Can you please try to run it from a "normal" cmd? (BTW do you have WinFsp installed?) Thanks. |
I had the same issue. Turned out the driver was not installed correctly (yellow exl. mark) |
I have WinFS installed, its dev stuff was necessary for compilation. What was the proper way to install the drivet? Mine seems fine, win is in testing mode |
Does running with debug logs (virtiofs.exe -d -1 -D -) show useful information? I'm using the Device Manager to install the driver (Right-click on the Mass Storage Device and Install Driver). Windows should be with "bcdedit /set testsigning on" (and follow with a reboot), the driver file should be self-signed with a certificate that is in the Trusted Root Certificate store. Double-click on the driver after it was installed should show "This device is working properly." in the Device status. |
Yep. You should sign the viofs.sys file and install the certificate you signed the driver with to the "Trusted Root Certificates" store. |
Ok, I'm trying to figure it out, MS documentation is particularly obtuse |
Ok, driver installed, service installed, no error, but now I'm getting this on the host side
or when started as root
|
thank you |
What command line are you using to run qemu? It should include something like:
|
The doc that I was following lacked the |
It works! I just had to adjust memory of -object memory-backend-file to match systems memory. |
Nice ;-).
Virtio-fs is not a read-only file system. What are the permissions of the shared folder on the host side? Do you mean Windows crash? Or QEMU? If it Windows can you send me the Windows coredump? It will help me if you can explain with a bit more details on how to reproduce it.
I'm not sure what you mean here. Is it too slow? |
I meant that it's fast. Is there plan to enable it RW eventually? |
It is RW now. At least on my setup...
Cool. Do you have a coredump? |
Oh, nvm about RW then, I've read you wrong. |
Hi, today I installed virtiofs dirver from fedora ISO v0.1.187 and had some fun with it. Steps to reproduce:
|
@tkolo Yes, there seems to be some problems with permissions. Even if I use the permissions of 777, I can only create a folder, not create new text in the created folder. |
With permission 777 on the host folder, I have strange behavior in the guest windows:
So it looks like the file creation is repeated many times. |
This
This issue seems to be related to WinFSP actually. I have the exact same issue with sshfs-Win and WinFSP. If I run the VM under VirtualBox it works properly. If the same VM (converted) runs under KVM I have the issue. Tried to do a research but found nothing. Weird the same approach works in VBox but not KVM. Some driver issue perhaps. |
Excuse me, is there any progress? |
I am also experiencing the same issue. I'm not very familiar with how this stuff works, but might this be related: winfsp/winfsp#204? |
I have the same symptoms as Aetf above. |
I figured it is simply not usable on Windows. Tried all of the available methods and the only way to get this working is the samba. Not happy about it but it works ok. |
https://virtio-fs.gitlab.io/howto-windows.html |
I tend to believe this issue has been finally solved. |
@marcello-pietrobon I compiled the virtiofs.exe of the master branch. |
Hmm, read/write works when you manually start virtiofs.exe manually from an command shell but is read-only when started as a service. 🤷♂️ For the moment I just created a batch file in |
Hi @Dave--G,
This sound like an issue we had and was resolved. Does you virtiofs service file included commit #525 ?
Thanks,
|
I'm using virtiofs from virtio-win version 190 obtained here https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.190-1/ which appear to be dated 2020/11/24. It may not contain commit #525 (?) Is a more recent signed build available? I'm looking and can't find anything more recent. Thanks |
I have similar issues regarding write access to the host with virtio-win 208, running a Windows 10 20H2 guest on an Ubuntu 20.04.3 host, and reported them to the virtiofs mailing list, see https://listman.redhat.com/archives/virtio-fs/2021-October/msg00185.html. I use a shell (Windows CMD or Cygwin bash) with Administrator rights on the guest |
The service VirtIO-FS has failed to start (Status=c00000008) 🤷 will installing a newer version of windows (eg win11) help anything here? or be a waste of time? |
Hi @dreamcat4,
Could you please show your libvirt virtiofs XML configuration? It should look something like that:
You're right, it will be a waste of time. |
lol thanks so much man! yeah it was wrong config there... <filesystem type="mount" accessmode="mapped">
<source dir="/tmp/share"/>
<target dir="/share-vfiofs"/>
<readonly/>
<alias name="fs0"/>
<address type="pci" domain="0x0000" bus="0x06" slot="0x00" function="0x0"/>
</filesystem> so i changed edited to match yours. Then it said SHM was disabled. Great! because now I can go enable that in the CPU config tabs. And it should then appear in the guest. Which is a fantastic progress. ...not to say it wont still be broken for whatever other reasons, but at least can get a bit further along the journey. Thanks so much! Very grateful |
This is because memory should be also configured in a proper way: <memoryBacking>
<source type="memfd"/>
<access mode="shared"/>
</memoryBacking> |
yep, just added it in. after finding it a linux guide page for virtiofs https://libvirt.org/kbase/virtiofs.html [EDIT] it worked! thanks so very much @viktor-prutyanov |
I come to the conclusion that this still needs some thinking before it works. My intent is to share a file system from the linux host to the windows guest. I think I am not the only one in this case. But the windows Guest is using/seeing an NTFS file system and the linux host is seing an ext4fs (or other unix) filesystem. Therefor the first question is how is the user in windows guest mapped to the user in linux host? But just after.... when this will eventually work.... what about the fact that NTFS is case insensitive and the Unix FS is case sensitive? And so on.... Samba or NFS sharing through the network do this out of the box. The current virtiofs solution, lacks something to do the conversion. An idea could be to agree that the shared filesystem is an NTFS4G filesystem on the linux host. I did not tried, but I do not expect it to work OOB. Or may be a FAT32 filesystem.... But I expect that the virtiofs.exe component would need to be extended to take this into account. |
The case-insensitive issue is also tracked in downstream.
|
Hello All, Please help us understanding you use cases for using virtio-fs, and thus make us virtio-fs support better. Thanks a lot, |
Hmm, I've the problem that virtiofs.exe didn't start on windows 11. |
The question to original issue: https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/VirtIO-FS:-Shared-file-system Please don't mix different topics in one in issue. If anyone experiencing issues with virtio-fs, please open a separate issue. |
Just create a virtiofs service and set it to auto start, then reboot the system, all will be right. |
how to use virtiofs in Windows 10 guest?
I install VIRTIO FS Driver
The text was updated successfully, but these errors were encountered: