Hardware
VM hardware: (This is 2x what I read online that most people give it, so I presume it's sufficient)
What's weird (aside from crashing whenever I try to use VNC) is that pi-hole continues to work properly without any problems. VNC connection "triggers" something that causes it to die...?
Any ideas what could be wrong? Or what I should look at for diagnosing the problem?
- FreeNAS-11.3-U3.2
- 2x Xeon 2680v3 (12 cores, 24 threads each)
- Supermicro X10DRi-T4+ Motherboard
- 128 GB RAM
- 2x 2TB SSD in Mirror Pool
VM hardware: (This is 2x what I read online that most people give it, so I presume it's sufficient)
- 2 Cores
- 1 GB RAM
- 30 GB disk
- If it's shortly after booting the VM then it works fine. I can use VNC, do stuff on the console, disconnect, re-connect, etc. No problems.
- If I wait a few hours, then when I try to connect with VNC it fails to connect. Then the VM presumably crashes, because when I go back to the Virtual Machine listing it has stopped.
- I then restart the VM, and everything is working again. Until a few hours passes... and the cycle repeats.
What's weird (aside from crashing whenever I try to use VNC) is that pi-hole continues to work properly without any problems. VNC connection "triggers" something that causes it to die...?
Any ideas what could be wrong? Or what I should look at for diagnosing the problem?