This is one of those 'don't do it' things.
Running a VM over a network is absolutely not recommended. It's not just performance - any network glitch at all will corrupt the VM, often into an unrecoverable state. Use an external hard drive instead.
I have to add, using the same configuration with workstation pro on a windows 10 machine, didn't had any issue for months.
Same share, same disks, same NAS.
Issue started with moving the Host to a Mac fusion product.
The NAS can also handle NFS but afaik I can use it only on esxi products.
Anyway, the issue is not with the guest machine. I accept the risk of using it over a network. The issue is with the Host faulting and rebooting. The host. If any network error, I expect the host warning me of a failed read/write operation, but not reboot itself out the blue.
Hope I added more info about the issue.
Got a fault even with the VM on local disk.
Fusion was installed over a previous installation (updating version) that comes from a time machine restore (I purchased a new mac mini and then restored the time machine of dismissed device on the new device).
I now did fully unstalled Fusion (following this procedure)and done a "clean install" to rule out any wrong settings from previous installation.
Ahh, yeah, time machine is unreliable for full restores. Between silent corruption and missing files, there's often challenges. Using the migration wizard is more reliable, but at that point, it's best just to migrate directly from one machine to another.
After a clean (re)install, the VM didn't had any issue so far.
Yep, I now had take note about the troubles that may arise between full Time Machine restores and some software!