none
Dual Processors, Hyper-Threading Technology, and Multi-Core Systems and Hyper-v

    Question

  • I would like to ask if there is any know issue on the Dual Processors, Hyper-Threading Technology, and Multi-Core Systems and Hyper-v,

    I have hyper-v on R610 2(quad-core e5530) enabled Hyper-threading on top the core and installed hyper-v, assigned the 16 cpu’s to the VM.

    source: http://www.microsoft.com/downloads/details.aspx?FamilyID=91e2e518-c62c-4ff2-8e50-3a37ea4100f5&DisplayLang=en

    Hypervisor Functional Specification

    1.1.1       Hyperthreading

    Multiple virtual processors can optionally be grouped together and scheduled onto hyperthreads within a single physical processor core. In effect, these virtual processors then act like virtual hyperthreads. When virtual processors are grouped as such, the hypervisor tries to schedule them concurrently on the same physical processor core. This scheduling behavior potentially improves performance and reduces information leakage across partition boundaries.


    Here is the BSOD using the hyper-threading enabled, if we disabled the hyper-threading the problem is gone.

    0: kd> vertarget

    Windows 7 Kernel Version 7600 MP (16 procs) Free x64

    Product: Server, suite: Enterprise TerminalServer SingleUserTS

    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

    Machine Name: "HYPERV"

    Kernel base = 0xfffff800`01619000 PsLoadedModuleList = 0xfffff800`01856e50

    Debug session time: Sun Aug 30 17:52:16.082 2009 (GMT-7)

    System Uptime: 0 days 7:04:00.808

     

    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: 000000000000000d, Clock interrupt time out interval in nominal clock ticks.

    Arg2: 0000000000000000, 0.

    Arg3: fffff88002315180, The PRCB address of the hung processor.

    Arg4: 0000000000000008, 0.

     

    0: kd> dt fffff88002315180 nt!KPRCB

       +0x000 MxCsr            : 0x1f80

       +0x004 LegacyNumber     : 0x8 ''

       +0x005 ReservedMustBeZero : 0 ''

       +0x006 InterruptRequest : 0 ''

       +0x007 IdleHalt         : 0x1 ''

       +0x008 CurrentThread    : 0xfffff880`023202c0 _KTHREAD

       +0x010 NextThread       : 0xfffffa80`2d1e9060 _KTHREAD

       +0x018 IdleThread       : 0xfffff880`023202c0 _KTHREAD

     

    1: kd> !thread 0xfffff880`023202c0

    THREAD fffff880023202c0  Cid 0000.0000  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 8

    Not impersonating

    DeviceMap                 fffff8a000006100

    Owning Process            0       Image:         <Unknown>

    Attached Process          fffffa8012dca040       Image:         System

    Wait Start TickCount      0              Ticks: 1630810 (0:07:04:00.799)

    Context Switch Count      2402264            

    UserTime                  00:00:00.000

    KernelTime                07:00:48.356

    Win32 Start Address nt!KiIdleLoop (0xfffff800016936a0)

    Stack Init fffff8800233ddb0 Current fffff8800233dd40

    Base fffff8800233e000 Limit fffff88002338000 Call 0

    Priority 16 BasePriority 0 PriorityDecrement 0 IoPriority 0 PagePriority 0

    Child-SP          RetAddr           : Args to Child                                                           : Call Site

    fffff880`0233db88 fffff800`01c0a401 : 00000000`00000000 fffff880`0233dbf0 00000000`000000df 00000000`00000020 : hal!zzz_AsmCodeRange_End

    fffff880`0233db90 fffff800`01bfd380 : fffff880`02315180 0000375f`00000000 00000000`000007bc fffff800`01c1ab50 : hal!HalpResetThisProcessor+0x1dd

    fffff880`0233dbc0 fffff800`016873f3 : fffff880`02315180 fffff880`0233dc70 fffff880`023202c0 fffffa80`2e5d9b60 : hal!HalpApicRebootService+0x58

    fffff880`0233dbf0 fffff800`016936d2 : fffff880`02315180 fffff880`00000002 00000000`00000002 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163 (TrapFrame @ fffff880`0233dbf0)

    fffff880`0233dd80 00000000`00000000 : fffff880`0233e000 fffff880`02338000 fffff880`0233dd40 00000000`00000000 : nt!KiIdleLoop+0x32

     

    fffff800`01c0a3fb fa              cli

    fffff800`01c0a3fc e82f920000      call    hal!HalpHalt (fffff800`01c13630)

     

    1: kd> u fffff800`01c13630

    fffff800`01c13630 f4              hlt

    fffff800`01c13631 c3              ret   <----

     

    0: kd> !sysinfo machineid

    Machine ID Information [From Smbios 2.6, DMIVersion 38, Size=4522]

    BiosMajorRelease = 1

    BiosMinorRelease = 0

    BiosVendor = Dell Inc.

    BiosVersion = 1.0.4

    BiosReleaseDate = 03/09/2009

    SystemManufacturer = Dell Inc.

    SystemProductName = PowerEdge R610

    BaseBoardManufacturer = Dell Inc.

    BaseBoardProduct = 0J352H

    BaseBoardVersion = A00

     

    0: kd> !sysinfo cpuinfo

    [CPU Information]

    ~MHz = REG_DWORD 2394

    Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

    Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0

    Identifier = REG_SZ Intel64 Family 6 Model 26 Stepping 5

    ProcessorNameString = REG_SZ Intel(R) Xeon(R) CPU           E5530  @ 2.40GHz

    Update Signature = REG_BINARY 0,0,0,0,11,0,0,0

    Update Status = REG_DWORD 0

    VendorIdentifier = REG_SZ GenuineIntel

    MSR8B = REG_QWORD 1100000000

     

    1: kd> !cpuinfo

    CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features

     0  6,26,5 GenuineIntel 2394 0000000f00000000                   211b3dfe

     1  6,26,5 GenuineIntel 2394 0000001100000000                   211b3dfe

     2  6,26,5 GenuineIntel 2394 0000000f00000000                   211b3dfe

     3  6,26,5 GenuineIntel 2394 0000001100000000                   211b3dfe

     4  6,26,5 GenuineIntel 2394 0000000f00000000                   211b3dfe

     5  6,26,5 GenuineIntel 2394 0000001100000000                   211b3dfe

     6  6,26,5 GenuineIntel 2394 0000000f00000000                   211b3dfe

     7  6,26,5 GenuineIntel 2394 0000001100000000                   211b3dfe

     8  6,26,5 GenuineIntel 2394 0000000f00000000                   211b3dfe

     9  6,26,5 GenuineIntel 2394 0000001100000000                   211b3dfe

    10  6,26,5 GenuineIntel 2394 0000000f00000000                   211b3dfe

    11  6,26,5 GenuineIntel 2394 0000001100000000                   211b3dfe

    12  6,26,5 GenuineIntel 2394 0000000f00000000                   211b3dfe

    13  6,26,5 GenuineIntel 2394 0000001100000000                   211b3dfe

    14  6,26,5 GenuineIntel 2394 0000000f00000000                   211b3dfe

    15  6,26,5 GenuineIntel 2394 0000001100000000                   211b3dfe

                          Cached Update Signature 0000001100000000

                         Initial Update Signature 0000001100000000

     

    Tuesday, October 13, 2009 6:40 PM

Answers

  • Hi,

     

    According to the description, we find it seems to be system crash issue and we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. Therefore, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Hope the issue will be resolved soon.

     

    Best Regards,

    Vincent Hu

     

    Tuesday, October 20, 2009 8:39 AM

All replies

  • Hyper-V or Hyper-V R2? The R2 version has several improvements.
    Wednesday, October 14, 2009 1:13 AM
  • Hi,

     

    According to the description, we find it seems to be system crash issue and we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. Therefore, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Hope the issue will be resolved soon.

     

    Best Regards,

    Vincent Hu

     

    Tuesday, October 20, 2009 8:39 AM
  • How about below?

    Stop error message on an Intel Xeon 5500 series processor-based computer that is running Windows Server 2008 R2 and that has the Hyper-V role installed: "0x00000101 - CLOCK_WATCHDOG_TIMEOUT"
    http://support.microsoft.com/kb/975530/en-us
    Sunday, December 20, 2009 12:34 AM
  • Hi,

     

    We have the setup of 6 node Hyper-V cluster and we are getting same memory dump on one of the node. Just wanted to know that we need to apply this hotfix on all the nodes or only the problematic node.

    Wednesday, June 30, 2010 12:30 PM