2012 VM间歇性地锁定解决

5年前
2016年1月30日
5个答复
1299意见

UserLevel 2

+13

西顿
开拓者
15个答复

我与我迁移的一些2012 VM遇到了间歇性问题，这些VM在随机的时间后一直锁定，通常为100％CPU和所有IO停止。VM控制台无响应，网络无法到达，重置仅是使重新在线的解决方案。然后，它将再次运行几分钟，几个小时，甚至一天或更长时间，只是在白天或黑夜随机做同样的事情，因此没有逻辑上的patt。

我最终将其跟踪到时区配置问题，当重新启动有关VM时，TimeZone将其时钟设置为高空主机时间，该时间在不同的时区（默认TZ节点已运送）到主机VM TZ。过去，我遇到了类似的问题，尽管不是主机锁定，其中许多主机会浪费时间同步，并且在我们的Citrix Xenserver群集群集主机上的主机和VM之间的tz差异都会消失。由于我们的VM位于广告域上，因此他们将超出NTP调整范围，因为时间差太大。

作为我的集群设置的一部分，我将集群时区更改为与我的（澳大利亚/珀斯）相同。但是未能做AHV主持TZ。

在更改AHV主机以纠正TZ并重新启动VM之后，现在似乎还不错，并且不再是主机锁定，也每次重新启动后的正确时间

\n
\nI endup tracking it down to a timezone config issue, when rebooting the VMs in question the timezone would set their clock to the hypervisior host time, which was in a different timezone (default TZ nodes were shipped with) to the the host VM TZ. I had a similar problem in the past, although not with the host lockups, where a number of hosts would lose time sync and be out by the TZ difference between host and VM on our Citrix XenServer Cluster hypervisor host. Because our VM are on an AD domain they will be out of NTP adjustment range becasue time difference was too big.
\n
\nAs part of my cluster setup I had changed the cluster timezone to be same as mine (Australia\/Perth). but failed to do the AHV hosts TZ.
\n
\nAfter changing AHV hosts to correct TZ and Rebooting VMs, all appears to be fine now and no more host lockups, also on the correct time after reboots each and every time 😉","quoteUsername":"seaton","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">