johnsanc

Yes, same here. Unfortunately I cannot find anything useful in any logs that even gives a clue. Perhaps @SimonF has a suggestion for where to look, or maybe he can reproduce the issue as well?

Thanks for confirming I’m not the only one. I just checked and all my CPUs assigned to that VM are pegged as well once the freeze occurs. i tried disabling the VirtIO-FS service in windows and it still freezes, so that sounds more like a host problem. Perhaps some configuration issue in the XML or bug? I’m open to suggestions since Virtiofs is sooooooo much faster than SMB shares for my use cases. I would love if we could get this VM freeze issue resolved.

Posted in General the other day figured this is a better place to ask along with more details... so apologies for the double post as it doesn't look like I can move a topic. I upgraded to UnRAID 6.11.1 and everything went smoothly. However my Windows 10 VM just freezes without any apparent errors as far as I can tell. There is nothing suspicious that I can see in the Windows Event Viewer logs and I don't see anything different in my VM log compared to when it was working fine. I used to have issues after I upgraded to 6.11.0 where the network connection to the VM would drop, but I resolved this by upgrading the virtio drivers to the ones from the latest stable ISO. This issue with 6.11.1 is different though, and I can tell the VM is completely frozen. I usually use RDP for accessing the VM, but if I plug in a monitor the graphics card I have passed through to the VM I can see the time on the windows lock screen is frozen. The only major change I did was enabled the virtiofs feature. I've attached my diagnostics in case anyone can take a peek to see what the issue might be. I am not really sure where to look. My VM froze around 11:29 PM ET on 10/9/22 and again at 10:53 AM ET on 10/10/22. Basically it looks like the VM will not stay live for more than 2-3 hours without completely freezing and requiring me to force stop. I did notice that if I try to do a regular stop once its frozen the libvirt log shows the following: 2022-10-10 14:57:38.384+0000: 520: error : qemuAgentSend:759 : Guest agent is not responding: Guest agent not available for now 2022-10-10 14:58:14.162+0000: 519: error : qemuAgentSend:759 : Guest agent is not responding: Guest agent not available for now 2022-10-10 14:58:56.600+0000: 521: error : qemuAgentSend:759 : Guest agent is not responding: Guest agent not available for now 2022-10-10 14:59:27.392+0000: 521: warning : qemuDomainObjTaintMsg:6464 : Domain id=2 name='Windows 10' uuid=8dd0454f-e9f4-6e94-3bc2-93cbd146abcb is tainted: custom-ga-command 2022-10-10 14:59:32.393+0000: 521: error : qemuAgentSend:759 : Guest agent is not responding: Guest agent not available for now Any ideas? tower-diagnostics-20221010-1112.zip

I upgraded to UnRAID 6.11.1 yesterday and everything went smoothly. However my Windows 10 VM appears to have stability issues and just freezes without any apparent errors as far as I can tell. There is nothing suspicious that I can see in the Windows Event Viewer logs and I don't see anything different in my VM log compared to when it was working fine. I used to have issues after I upgraded to 6.11.0 where the network connection to the VM would drop, but I resolved this by upgrading the virtio drivers to the ones from the latest stable ISO. This issue with 6.11.1 is different though, and I can tell the VM is completely frozen. I usually use RDP for accessing the VM, but if I plug in a monitor the graphics card I have passed through to the VM I can see the time on the windows lock screen is frozen. The only major change I did was enabled the virtiofs feature. I've attached my diagnostics in case anyone can take a peek to see what the issue might be. I am not really sure where to look. tower-diagnostics-20221009-1805.zip

Thanks for confirming, just for reference I also reported that here: https://github.com/virtio-win/kvm-guest-drivers-windows/issues/839

Make sure you don't have another network drive or something mapped to Z:, the Virtio-FS service does not handle drive letter conflicts. See my thread here for more details / troubleshooting Virtio-FS with windows: Also, potential bug report here for the service restart issue I was encountering: https://github.com/virtio-win/kvm-guest-drivers-windows/issues/839

Did that resolve the restart issue for you? Or even with the dependencies you still have the restart issue?

One other thing to note... the documentation shows to register the service with a dependency, but I already had the VirtIO-FS service active before enabling any of this, and it had no dependencies, so to modify that service for good measure I did this from an elevated command prompt: sc config VirtioFsSvc depend="WinFsp.Launcher/VirtioFsDrv" Didn't seem to resolve the broken user on restart though.

OK so I figured out how to break it... stop your VirtIO-FS service and restart it. It will behave improperly with that broken S-1-5-0 user. Can you confirm? I think yesterday I was running into issues because I was stopping and starting services and changing drive letters. But it looks like if you let it start up automatically and don't stop it it works correctly.

Well this is bizarre... last night my VM froze with nothing in the logs or event viewer, so I forced restarted it today and now I just did another check and I can see that it does work correctly exactly as you show in your screenshot above. Yesterday I was getting everything with that S-1-5-0 user. I have no idea what would have changed to make it work differently today...

I am currently using a local account with administrator privileges and it does not work for me. Are you sure you can copy a folder of files to the mounted drive? If so, how do the permissions of the copied folder/files look on the host machine after you copied them? I hate windows permissions.

Yes I am currently just mounting /mnt/user/ for now to keep it simple until the signed drivers support the mount tag. I changed my registry key to a different drive letter though to avoid conflicts with my other mapped network drives. That worked fine. Info here on how to do that: https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/VirtIO-FS:-Shared-file-system#options So far everything seems to work great and the performance for me at least is MUCH better than SMB with a ton of small files, but the permissions issues are currently a show stopper.

Excellent thanks for the update. Yeah it just took me a few minutes to realize the mount tag parameter wasn't supported yet. Hopefully we can get to the bottom of the permissions issues... otherwise this is basically unusable for basic Windows use cases. Im not sure if its a virtiofs issue or winfsp issue, or if theres some special configuration or way to make it play nice. Also, just to clarify, for my results above I used an extra SMB configuration to force the user/permissions that I want and its worked great for years. I am hoping we can do something like that with virtiofs/winfsp. [global] security = USER guest account = nobody public = yes guest ok = yes map to guest = bad user force user = nobody force group = users force directory mode = 0777 force create mode = 0666 create mask = 0666

Another update - Permissions are also an issue and I haven't quite figured that one out yet. I tried a few basic tests like copying a folder of files from VM to the mounted drive and it did not work. it created the folder with 775 permissions but then none of the files within the folder could be copied. If anyone has any ideas I'm all ears. A few tests I did: - create folder with smb: nobody/users, 777 - create file with smb: nobody/users, 666 - create folder with virtiofs: nobody/users, 775 - create file with virtiofs: nobody/users, 664

Apparently this is a very new feature that hasn't made its way into any of the standard driver ISOs yet. https://github.com/virtio-win/kvm-guest-drivers-windows/pull/804 I guess I'll stick with a single share for now to avoid the headaches.

So it works correctly if I mount a single share, but if multiple are included it seems to map a random share to the Z: drive. How can you properly map multiple shares? I tried the instructions here but whenever I try to start the virtiofs service the console looks ok, but then I see errors in the event viewer: Console log used, where "games" is a mount tag specified in the XML "C:\Program Files (x86)\WinFsp\bin\launchctl-x64.exe" start virtiofs viofsY games Y: Event Viewer error: virtiofs: The service VirtIO-FS has failed to start (Status=c0000001). Has anyone got this to work correctly for multiple shares?

EDIT: I was able to get this to work by removing a network drive I had mapped to Z: Apparently this service does not manage any drive letter conflicts correctly.

Posting this here because I don't want to clutter up the announcement thread.... but how do you get virtiofs to work with a Windows 10 VM? The form composer created this for the settings: <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs' queue='1024'/> <binary path='/usr/libexec/virtiofsd' xattr='on'> <cache mode='always'/> <sandbox mode='chroot'/> <lock posix='on' flock='on'/> </binary> <source dir='/mnt/user/'/> <target dir='shares'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </filesystem> I tried manually adding this to the XML which got around the startup error: <memoryBacking> <nosharepages/> <source type='memfd'/> <access mode='shared'/> </memoryBacking> But now what? I have winfsp installed and in Windows I can see there is a "VirtIO-FS Service". If I start that service nothing seems to happen. I expected to see a new drive letter mounted once the service starts. Is there some additional steps that are required? @SimonF - Any thoughts?

I noticed something peculiar. Sometimes files modified over a SMB share are written with an Access timestamp that displays 12:00:00 AM when viewing properties of the file. When when I check the timestamp on Unraid it appears these files are set to Sep 13 30828. I am able to reproduce this fairly consistently if I modify the file shortly after its creation time, within about a minute. What is causing this invalid access timestamp to be written? Is this a known bug? Is there any way to resolve? There are a few Windows apps I use that do not handle this scenario properly. Any insight is appreciated!

Hmmm... I'm going to have to dig deeper into my dockers. When the Docker service is disabled, I can clear the ARP table and I get the correct MAC address. If I I start the docker service, clear the ARP table again, then I get the weird random MAC address. EDIT: Ok the MAC address I am seeing in pfSense when I turn on the Docker service is the one from "shim-br0". I assume this is because I have "Host access to custom networks" enabled in my Docker settings. I believe I only needed this for Pi-Hole, but now I replaced that with pfBlockerNG. Once I disabled the custom networks I saw my correct MAC address in pfsense.

I recently added a pfSense box to my network and assigned some static IP addresses. I see in my pfSense logs a ton of entries like this: arp: xx:xx:xx:xx:xx:xx attempts to modify permanent entry for 192.168.y.yyy on igb1 It looks like something is changing my Unraid MAC address to the address represented by xxx's above. I thought maybe it was my pihole docker, but I deleted that since I no longer need it. Upon each reboot I get a different random and unique MAC address for Unraid. Any ideas what could be causing this?

Forgot to followup but I got it working. I turned my old router to an AP and setup a pfSense box. I forgot to add the static route in pfSense. Once I added it things worked perfectly.

I tried adding my router IP and 8.8.8.8 to the Peer DNS Server and it did not allow me to access anything aside from my LAN when using "Remote Tunneled Access". Any idea what the issue could be? EDIT: Apparently if I use NAT then I can access the internet using Remote Tunneled Access. Is there a way to make that work without the NAT setting set to "Yes" ?

I am really struggling with this one and must have read though this entire thread 3 times now. Here is what I have so far: Local server uses NAT: No Local endpoint: my external IP : 51820 Peer type of access: Remote tunneled access All local tunnel/peer settings are defaults My docker config is set to allow host access to custom networks The docker IPv4 custom network I have uses the same subnet I forwarded port 51820 to my unraid server internal IP I added a static route in my router: Destination IP: 10.253.0.0 IP Subnet Mask: 255.255.255.0 Gateway IP: unraid internal ip address Metric: 2 (No idea what this is for and Netgear's help is not helpful - supposedly this is supposed to be the number of routers on the network?) Now, when I try to ping 10.253.0.1 with the command line it works: PING 10.253.0.1 (10.253.0.1): 56 data bytes 64 bytes from 10.253.0.1: icmp_seq=0 ttl=64 time=1.303 ms 64 bytes from 10.253.0.1: icmp_seq=1 ttl=64 time=2.949 ms 64 bytes from 10.253.0.1: icmp_seq=2 ttl=64 time=2.096 ms 64 bytes from 10.253.0.1: icmp_seq=3 ttl=64 time=2.886 ms 64 bytes from 10.253.0.1: icmp_seq=4 ttl=64 time=3.213 ms 64 bytes from 10.253.0.1: icmp_seq=5 ttl=64 time=2.095 ms When I try to ping 10.253.0.2 I get "Destination Host Unreachable" errors but I can also see that the errors show that the Redirect Host is going to my unraid server IP. I tried connecting with both my iPhone and the macOS WireGuard app and both show the 5 second timeout handshake error. Anyone have any suggestions? I feel like I have to be missing something obvious. EDIT: I completely forgot about my piece of hot garbage AT&T Pace gateway for my fiber connection. Since AT&T's firmware update broke DMZ+ mode a year ago (still not fixed) I had most ports opened to my Netgear router... but the range ended at 50999 since AT&T has a few service ports reserved above that. I changed my Wiregaurd port to something in range of what I forwarded and it worked without a hitch. However, how do I access both my LAN and the internet at the same time on the VPN? Do I need to select a different "peer type of access"? EDIT2: - Remote tunneled access = LAN access + no interwebs on device I'm using to VPN in - Remote access to LAN = LAN access + interwebs

@bastl - Not sure if there is a configuration somewhere to avoid symlinks. I just divided my external storages up so they didn't include anything that would update frequently or include any symlinks.