To work around this issue for virtual machines migrated to an ESXi 6.5 host from earlier version, recover the virtual machine from the ESXi 6.5 host and set Numa.FollowCoresPerSocket to 1 on all ESXi 6.5 hosts.
Symptoms:
VMware vSphere ESXi 6.5
vSphere 6.5 has optimized the vNUMA layout for NUMA-aware virtual machines based on the physical NUMA configuration. In some cases, a virtual machine may see a different vNUMA topology after migrating to the destination ESXi 6.5 host from the vNUMA topology on the source ESXi host. Failing to recognize the change on the destination host (6.5) may lead to a host purple diagnostic screen or VMM panic during vMotion of the virtual machine.
This issue occurs if the virtual machine which is migrated contains custom VMX settings, such as cpuid.corePerSocket or numa.autosize.once.
This issue is resolved in ESX 6.5.0a, available at Broadcom Downloads.
To work around this issue for virtual machines migrated to an ESXi 6.5 host from previous version, recover the virtual machine from the ESXi 6.5 host and set Numa.FollowCoresPerSocket to 1 on all ESXi 6.5 hosts:
To recover virtual machines that were migrated to a ESXi 6.5 host:
To manually set the Numa.FollowCoresPerSocket to 1 on the ESXi 6.5 hosts: