tag:blogger.com,1999:blog-5976686513564131325.post4768008888552774888..comments2024-03-17T15:34:05.492-06:00Comments on MPECS Inc. Blog: Hyper-V On Nehalem CPUs Error – CLOCK_WATCHDOG_TIMEOUT Critical HotfixPhilip Elder Cluster MVPhttp://www.blogger.com/profile/06082028960643490292noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5976686513564131325.post-7695743429459519432009-12-26T10:05:31.622-07:002009-12-26T10:05:31.622-07:00Sven,
After the hotfix was applied we had a coupl...Sven,<br /><br />After the hotfix was applied we had a couple of weird VM service lockups but the OS kept running.<br /><br />Once through that though, we have stood up a number of recovery based OSs as well as fresh OS installs and had them running contantly with no more issues.<br /><br />The C3 state and other BIOS settings related to the Nehalem Turbo and Sleep states are fully enabled.<br /><br />We are standing up an Intel Flex Server (Modular) this week to run a Hyper-V cluster on. So, you can bet that there will be a lot of testing going on before we go live!<br /><br />PhilipPhilip Elder Cluster MVPhttps://www.blogger.com/profile/06082028960643490292noreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-52060183379259782462009-12-26T02:15:35.400-07:002009-12-26T02:15:35.400-07:00Hi Philip,
"The update begs the question tho...Hi Philip,<br /><br />"The update begs the question though, does the hotfix really resolve the conflict with the CPU architecture?"<br /><br />I have indeed exactly the same question, considering i'm in the proces of buying ourselves two servers (with Nehalems) and a san (to setup a hyper-v failover cluster on Windows Server 2008 R2). The fact that this issue seems to be intermittent and i've read conflicting reports about this, worries me also. So i'm curious about your evaluation whether or not this hotfix does what it promises.<br /><br />Sven WillemenAnonymousnoreply@blogger.com