I am trying to run vm-curator from a fedora 44 host with the binary package and qemu and alike dependencies layered in. I cannot use folder sharing between windows 11/fedora kde guest and host. To my knowledge, vm-curator uses virtio-9p for file share, I did botht try selinux contexts and disabling selinux, yet nothing helped. I did even run launch.sh scripts from the terminal to see any errors, the everything seems fine with the exception of lacking functionality, any ideas for what I can do?
I think the issue with Windows 11 is that vm-curator uses virtio-9p for shared folders and Windows doesnt have a usable 9p driver so even if QEMU exports the share Windows cant mount it
For Fedora KDE 9p should work but you need to mount it manually inside the guest using the tag from vm-curator
For Windows I think using SMB instead of 9p would be the easiest workaround
I would be okay with a samba share (it would make it simpler for fedora guest as well) Is there an easy and convient way of setting up a samba share that is not tied to the launch.sh script and is only accesible to vms and host?
you can set up a regular samba share on the host without modifying launch.sh
first test if the guests can reach the host through 10.0.2.2
on the host run
python3 -m http.server 8000 --bind 127.0.0.1
then from the windows guest run this in powershell
Test-NetConnection 10.0.2.2 -Port 8000
for fedora you can run nc -zv 10.0.2.2 8000
if the test succeeds you can set up samba on the host
since youre using kinoite install samba using
rpm-ostree install samba
then reboot and create the shared folder and samba password
mkdir -p ~/vmshare
sudo smbpasswd -a $USER
back up /etc/samba/smb.conf and configure it like this by replacing YOURUSER with your actual username
[global]
workgroup = WORKGROUP
interfaces = lo
bind interfaces only = yes
server signing = mandatory
map to guest = never
[vmshare]
path = /home/YOURUSER/vmshare
valid users = YOURUSER
read only = no
then enable home directory sharing for selinux and start samba
sudo setsebool -P samba_enable_home_dirs on
sudo systemctl enable --now smb
check that samba is listening only on localhost using
sudo ss -tlnp | grep smbd
in windows open \\10.0.2.2\vmshare and log in using your host username and samba password
for the fedora guest install cifs-utils and create the mount point
sudo dnf install cifs-utils
sudo mkdir -p /mnt/share
then mount the share
sudo mount -t cifs //10.0.2.2/vmshare /mnt/share -o username=YOURUSER,uid=$(id -u),gid=$(id -g)
replace YOURUSER with your host username and enter your samba password when prompted
if the initial connection test fails check the -netdev user line in launch.sh for restrict=on or custom network settings and check whether the vm uses passt or bridge networking
this should let both guests access the same host folder without tying the share to launch.sh
I did end up spinning up the samba with qemu since it was way easier and works; however, will mark synx’s mark as the solution since its more comprehensive, here is the lines I added to my config:
-netdev user,id=net3,net=10.0.4.0/24,smb=/path/to/dir \
-device e1000,netdev=net3 \
share accessible on \\10.0.4.4\qemu
nice ! glad you got it working and thanks for sharing the config.