Windows Server 2008 R2 with Hyper-V 環境執行 VM 發生異常重開機

　最近公司買進兩台 Server，要使用 Microsoft 的 Hyper-V，其中一台才運行幾天，卻發生有異常重新開機的現象。

　還好系統在 Windows 目錄下有產生 MEMORY.DMP 的檔案，可以使用 Windbg 來分析原因，經由 Windbg 分析結果。


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88001e5d180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88001e5d180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------

OVERLAPPED_MODULE: Address regions for 'VSApiNt' and 'VSApiNt.sys' overlap

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff800`070e5a28 fffff800`05a21453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`01e5d180 : nt!KeBugCheckEx
fffff800`070e5a30 fffff800`05a7bde7 : fffffa80`00000000 fffff800`00000002 00000000`00026160 fffffa80`11e18020 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff800`070e5ac0 fffff800`05fe9895 : fffff800`0600e460 fffff800`070e5c70 fffff800`0600e460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`070e5bc0 fffff800`05a6fc33 : fffff800`05bede80 fffff800`070e5c70 fffffa80`0cd3d780 00000000`00000011 : hal!HalpHpetClockInterrupt+0x8d
fffff800`070e5bf0 fffff800`05a7bec2 : fffff800`05bede80 fffff800`00000002 00000000`00000002 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`070e5d80 00000000`00000000 : fffff800`070e6000 fffff800`070e0000 fffff800`070e5d40 00000000`00000000 : nt!KiIdleLoop+0x32

STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------


　從 Windbg 分析結果來看，Unknown_Module、Unknown_Image 連 Windbg 也無法確定是什麼元件造成系統重新啟動。


　只好利用 "X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE" 關鍵字至 Google 搜尋看看，還好有找到一篇文章與我的狀況相同，依它的解決方法是將 BIOS 的「Hyper-Threading」關閉即可。


　目前已將 Hyper-Threading 關閉，還不確定是否有用，先觀察一陣子看看。




資料參考來源：http://www.ms-windows.info/Help/virtual-machine-keep-crashing-whole-29264.aspx