That model's not been supported since ESXi 5.5U3 sorry - it won't run 6.0 let alone 6.7.
Also don't use R5, it's been worthless for a decade, nobody uses it, it's essentially dangerous and manufacturers shouldn't even offer it.
Simple answer is yes. You just need to make sure they can talk to each other the same way you need to make sure computers on a network can talk to each other (i.e. compatible network settings).
Re your point 1 - there are a TON of settings that can be wrong, starting with firewall settings. The host talking to the VM is a VERY normal totally standard ...
That flamegraph of yours in static format, cropped to remove skinny deep stacks:
Yes, much of the on-CPU samples are system call related. Lots of poll() and the resulting read_tsc(), some read(), and apparently some system call overhead given time spent in system_call_after_swapgs().
Now this becomes a search for performance bugs and inefficiencies in all ...
I have a few ideas, I can't confirm whether they're actually what you're seeing though:
What version of VMFS are you running on each system? Older versions appear to handle large files (near 2tb) differently than newer ones.
Are there any volume healing operations you can try? It could be that the metadata on one or more of the disks is out of date and ...
Apparently, the bug is in openvm-tools, which sees the "6." in "7.6.1810" and reports it as CentOS 6. It is reported in the Red Hat Bugzilla as issue 1672087. They do not want to apply the patch since it does not apply to Red Hat, and CentOS only builds Red Hat sources, so the fix will not show up there.
However, once you upgrade to CentOS 7.7 (which should ...
The update manager is good, good way to learn it if you havnt yet. After the config you will know when update will be offered.
I always used the ISO for big update like in your case and left the update manager find all missing KB after. The why is some update is more of a reinstall over, then I prefer to have the latest driver built-in inside my ESX. Is it ...
To get batches of 10 you can use Select-Object with the parameters -First and -Skip:
$start = 0
$VMs |Select -First 10 -Skip $start |
Move-VM -Datastore $NewDatastore |
Select Name |Out-File -FilePath "c:\logfile" -Append
$start += 10
until ($start -gt $VMs.Length)
Appending to a file is just a parameter for Out-File.
So, the problem was that the AACRAID needed an update.
To find the proper bundle, you have to check VMware HCL for IO Devices:
I had to install the Adaptec_Inc_bootbank_scsi-aacraid_188.8.131.52.1.57013-1OEM.600.0.0.2494585 offline bundle and now my storage is back at last.
Next ESXi ...