TripKnot

Did you ever find a solution to this? I'm having the exact same issue. Old VM's have lost their network settings and new VM's show the network on creation screens only. Once created and go back to edit, networking is gone.

A probable reason why you are having trouble finding an inexpensive board with the number of PCIe slots you require is the cheaper Intel chipsets have only a limited number of PCIe lanes available and thus a limited number of PCIe slots. In the case of the Asrock C224 board you linked, the C224 chipset is limited to a total of 8 PCIe lanes. So one slot in use will run at best at x8 and two slots in use run both at x4 and would also disable the third. Obviously this board would severely limit your H200's which run in x8. You want to find which chipset has enough lanes to support your needs first, eg C236 has 20 PCIe lanes. Then find boards with that chipset and other features you need.

Try editing your server appdata/crashplan/conf/my.service.xml file, around line 23 may say: <serviceUIConfig> <serviceHost>127.0.0.1</serviceHost> If necessary, change this to: <serviceUIConfig> <serviceHost>0.0.0.0</serviceHost> This makes crashplan listen to non host clients without the use of the ssh tunnel. Restart the Crashplan docker and the Crashplan-Desktop docker should now connect without issue. As this is less secure, once logged into crashplan, change the security settings to require a password to use the client.

Those QNAP-looking 2/4/6/8-drive ITX chassis from U-NAS look like they are available in the US now at www.u-nas.com/cases.html Their store currently only has the 2 and 4 bay models and I'm hoping the 8 bay is available soon. Additional highres pics of the internals can be found here.