![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
robopet3Проблема обычная - почему-то не мигрируют VM между хостами кластера.
начало отладки находится тут:
vMotion fails to migrate between EVC clusters of ESXi host which have the same configuration (67666)
https://kb.vmware.com/s/article/67666
И затем:
https://peterc.tech.blog/
In my case the solution was very simple, we knew that for some reason one host was not capable of using the MDCLEAR CPU feature. Even though it was running the correct ESXi build and so should have the correct microcode (via the ESXi CPU microcode loading feature) and ESXi support for it.
I found a post suggesting that a cold start of the host maybe needed. So after completely powering down the host and powering it on again, the host worked correctly and the MDCLEAR CPU feature was available. vMotion to the host started working.
I’m not really sure why this worked but suspect for some reason, ESXi was not able to load the microcode on that host when it was last booted.
Another solution may have been to upgrade the BIOS to the latest release from the vendor, if available which includes the MDSCLEAR CPU feature.
И наконец
vim-cmd hostsvc/hostconfig|grep -A 2 MDCLEAR
esxcli system settings kernel get -s hyperthreadingMitigation
начало отладки находится тут:
vMotion fails to migrate between EVC clusters of ESXi host which have the same configuration (67666)
https://kb.vmware.com/s/article/67666
И затем:
https://peterc.tech.blog/
In my case the solution was very simple, we knew that for some reason one host was not capable of using the MDCLEAR CPU feature. Even though it was running the correct ESXi build and so should have the correct microcode (via the ESXi CPU microcode loading feature) and ESXi support for it.
I found a post suggesting that a cold start of the host maybe needed. So after completely powering down the host and powering it on again, the host worked correctly and the MDCLEAR CPU feature was available. vMotion to the host started working.
I’m not really sure why this worked but suspect for some reason, ESXi was not able to load the microcode on that host when it was last booted.
Another solution may have been to upgrade the BIOS to the latest release from the vendor, if available which includes the MDSCLEAR CPU feature.
И наконец
vim-cmd hostsvc/hostconfig|grep -A 2 MDCLEAR
esxcli system settings kernel get -s hyperthreadingMitigation
