none
Virtual machine keep crashing the whole Hyper-v environment RRS feed

  • Question

  • Hi,

    I just installed Hyper-v (2008 R2) on a brand new hardware (X3440 CPU + 16 GB server memory)

    On top of this, I installed one VM --> win7 (6GB RAM + 2 logic CPU)

    Whenever this win7 is running for a while (e.g. 2 hour of browsing internet through remote desktop), it will crash the whole thing, including the host Hyper-V server.

    I tried different things. I found if I change the VM's logic CPU to just one, the whole thing running OK. Is there any special configuration I have to do to make VM multiple logic CPUs running smoothly on Hyper-V server?

    By the way, I have Hyper-v server mini memory dump configured. and I check the memory dump file, it always gives me something like below:

    *******************************************************************************
    *                                                                             *
    *                        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: fffff88001fe1180, The PRCB address of the hung processor.
    Arg4: 0000000000000006, 0.

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


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

    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    PROCESS_NAME:  System

    CURRENT_IRQL:  d

    STACK_TEXT: 
    fffff800`02cc6a28 fffff800`0167d453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`01fe1180 : nt!KeBugCheckEx
    fffff800`02cc6a30 fffff800`016d7de7 : 00000000`00000000 fffff800`00000006 00000000`00026160 fffffa80`10161ac0 : nt! ?? ::FNODOBFM::`string'+0x4dfe
    fffff800`02cc6ac0 fffff800`01620895 : fffff800`01645460 fffff800`02cc6c70 fffff800`01645460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
    fffff800`02cc6bc0 fffff800`016cbc33 : fffffa80`0e586e98 fffffa80`0fa52000 fffff800`0184d7a0 00000000`00000002 : hal!HalpHpetClockInterrupt+0x8d
    fffff800`02cc6bf0 fffff800`016d7ec2 : fffff800`01849e80 fffff800`00000002 00000000`00000002 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
    fffff800`02cc6d80 00000000`00000000 : fffff800`02cc7000 fffff800`02cc1000 fffff800`02cc6d40 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
    ============================================

    Hopefully, some one from MS can shed light of this issue for me.

    Thanks a lot.

    -Simon

     

    Monday, December 6, 2010 1:44 PM

Answers

  • I fixed it.

    As long as I turn off Hyper-Threading from Hyper-v physical server BIOS (Xeon 3440 CPU), everything is ok now. (I can have multiple virtual CPU assinged to 2 or 3 VMs, running like a charm)

     

     

     

    • Marked as answer by Simon Pang Tuesday, December 7, 2010 5:10 AM
    Tuesday, December 7, 2010 5:10 AM