I’ve been beating my head against the wall on this one. I loaded KVM using Yast’s virtualization setup, then added qemu. I want to set up file sharing between a Windows 10 guest and my Tumbleweed host. It looks like everything is working in the guest using spice’s tools for Windows. I loaded the spice modules in Yast Software and set up the spice webdav in virt-manager. However, the spice-webdav service refuses to start. In vert-manager, the spice-webdav and spicevmc both say they are disabled when the guest is running.
When I try to start spice-webdav manually in Yast’s Services Manager, I get the following error: “Failed to open /dev/virtio-ports/org.spice-space.webdav.0: No such file or directory”
Sure enough, the directory is not there. How do I fix that? I don’t see any setup or initialization program for spice-webdav. I’ve tried reinstalling, but that doesn’t help. Anyone have any ideas? Thank you for your time.
Better to not use networking at all.
Instead share the filesystems.
https://en.opensuse.org/User:Tsu2/virtfs#Overview
For Windows Guests, instead of what is described, you should simply see your shared filesystem appear in your Windows Network Locations.
TSU
Thank you for your suggestion. Filesystem Passthrough was only offered as “Type: mount”. I set Driver as Path, Mode as Squash, Write as Immediate, Source as /home/user/Public, and Target as \Users\user\hostpublic. However, it doesn’t show up in the Win10 guest. I tried various Target formats, but nothing shows up in the guest. What am I doing wrong?
Should “just work.”
You’ve opened up File Explorer and in the bottom section expanded the entire tree?
TSU
Noticed something new which may be either an alternative or supercede the filesystem sharing I described.
I haven’t tested the following yet, but anyone doing this should take note
TSU
Thanks for the link. Very informative. BTW, it says that passthrough file access doesn’t work with Windows VMs because Windows doesn’t have the required drivers. I still haven’t gotten the file sharing to work. I’m giving up on Spice webdav because the Spice services always come up as disconnected on the host side, and attempts to restart them have been singularly unsuccessful. I’m going to give it a go with Samba. Everything else is great with the Windows 10 VM under QEMU/KVM. Performance is great.
Are you saying that after setting up using the steps described in my Wiki article,
In your MSWindows guest,
You open File Explorer,
Scroll down to the bottom where in the old, old WinXP days there used to be a “Network Neighborhood”
Expand the bottom node all the way
You don’t see your shared filesystem?
Although technically not actually on the NIC interface,
That’s how Windows Guests access filesystems exposed by the Plan 9 (9P) protocol, as though it’s a network share.
And yeah,
I recognize the spice protocol as useful in certain situations, but ordinarily I haven’t used it.
If you don’t intend to use the spice protocol, be sure you’re no longer specifying it in your connection string or setting.
TSU
I finally got the share to work using Spice WebDav. I used the virt-viewer to share the desired directory. That was the missing piece that I could not get to work before. I finally uninstalled all of KVM and QEMU, then reinstalled using Yast2 with the spice webdav being the only additional package that I added. Seems to work fine now. The file transfer is very slow, but it works. The host source shows up as drive Z. Works for me. I don’t do many transfers. Thank you for your time and assistance.