Linux virtual machines hangs after successful vMotion from ESXi 6.0 to 6.5
Article ID: 324640
Updated On:
Products
VMware
Issue/Introduction
Symptoms:
- Linux Virtual machines stops responding after successful vMotion from ESXi 6.0 to 6.5
- Virtual machine works fine once rebooted on 6.5 ESXi hosts
Cause
This issue occurs due to a difference in CPUID value for x2APIC post vMotion from ESXi 6.0 to ESXi 6.5.
Resolution
This issue is resolved in ESXi 6.5 Patch Release ESXi650-201811002, available at VMware Patch Downloads. For more information on downloading patch, see How to download patches in Customer Connect (1021623).
Workaround:
To workaround this issue if you do not want to upgrade, create DRS rules to separate virtual machines to make sure they either run on ESXi 6.0 hosts or ESXi 6.5 hosts in a Cluster with mixed ESXi versions
Workaround:
To workaround this issue if you do not want to upgrade, create DRS rules to separate virtual machines to make sure they either run on ESXi 6.0 hosts or ESXi 6.5 hosts in a Cluster with mixed ESXi versions
Additional Information
Feedback
Yes
No
Powered by
