Subj : Re: Test To : deon From : Apam Date : Fri May 27 2022 14:42:38 Re: Re: Test By: deon to Apam on Fri May 27 2022 01:52 pm de> I've not had any network issues that werent known about - and I generally de> use the VMware network (VMnet). The only (weird) issue with that is that de> it affects dockers vxlan's, so you need to turn off software checksums. de> That took a bit to diagnose and find an answer. de> I guess if the OS doesnt have a vmnet driver, then you have to go with one de> of the others... Yes, the virtual machines were using vmxnet3 or whatever the default VMWare virtual nic is, though I also tried e1000. The virtual machines (which were debian) ran fine with both those network cards until they stopped. In fact on my other computer with an Intel nic, everything worked without problems however, once I moved the VMs to the new PC with a newer model of intel nic, the vms kept dropping off the network. The google results I did find suggested it to be a problem with the ne1000 (ESXi's e1000 driver) (but they were results from 6.5 and suggested disabling ne1000 and falling back to an older driver which is no longer included with 7.0). Anyway, while I do like vmware esxi, now that I've moved everything over to KVM (and it's all running smoothly), I think I actually prefer this. I have Virt Manager on my desktop that connects to libvirt via ssh on the hypervisor and works well. I just today ordered another 16Gb of ram for it.. so should be able to replace all my other "servers" that I don't run because I can't justify the power usage :P Andrew --- SBBSecho 3.15-Linux * Origin: The Positronic Brain (1337:2/105) .