I've used bcdedit /set hypervisorrootproc to limit the number of cores the host OS can use on windows server 2016 for all my hyper-v servers. This helps free up processor resources to be used by guests. The initial couple of server 2019 servers
(i'm using for hyper-v hosts) that I've set hypervisorrootproc to limit cores lockup at boot and will never boot normally again until I go into safe mode and give the OS access to all cores. Has anyone experienced this yet? I haven't had time to
troubleshoot if it is specific to limiting to 2 cores vs 3 or 4 or if I limit cores at all.
↧