If after applying VMware vSphere (ESXi) security update - ESXi-6.7.0-20190504001-standard (Build 13644319) - https://kb.vmware.com/s/article/55636 and adding VMkernel.Boot.hyperthreadingMitigation = TRUE After restarting ESXi you notice half the number of logical processors (e.g. hyperthreading disabled!) - this is NORMAL!. "Enabling this option will result in the vSphere UI reporting only a single logical processor per physical core; halving the number of logical processors if Hyperthreading was previously enabled. In addition Hyperthreading may be reported as 'Disabled' in various configuration tabs."
BEFORE UPDATE VMkernel.Boot.hyperthreadingMitigation = false
AFTER UPDATE VMkernel.Boot.hyperthreadingMitigation = true
I blew-up my Linux server yesterday which runs Homebridge, by updating NodeJs from 12.x to 14.x! Whoops! What a mess, even trying to demangle and get working again! BUT Veeam Backup and Replication to the Rescue. with a feature, I've not used before
Why restore the VM, when you can just restore the changed blocks! and rollback the changes in the VM OS! from a backup!
first time I've used this function, and now my Homebridge server is working again!