2012年VMS间歇地锁定解决

5年前
2016年1月30日
5回复
1299次观看

UserLevel 2.

+13

座位
拓盘
15回复

我已经突破了一份局面的问题，我已经迁移了一个随机时间后一直在锁定，通常会增加100％CPU和所有IO停止。VM控制台没有响应和网络无法访问，重置只是解决方案返回在线。然后它将再次运行几分钟，小时，即使是一天或更长时间只能在一天或黑夜再次做同样的事情，所以没有逻辑PATTEN。

我最终将其跟踪到一个时区配置问题，当重新启动问题中的虚拟机时，时区会将其时钟设置为超级主机时间，它在不同的时区（默认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"}}}">