Sign in
Microsoft.com
 
System Center Virtual Machine Manager TechCenter
 
 
 
System Center Virtual Machine Manager TechCenter > System Center Virtual Machine Manager Forums > Virtual Machine Manager – Hyper-V > HyperV unstable vmms service crashes periodically
Ask a questionAsk a question
Search Forums:
 

AnswerHyperV unstable vmms service crashes periodically

  • Wednesday, August 13, 2008 2:54 PMTony de Sousa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

     

     

    I am getting an error, that is causing the hyperV to be unstable. I have 3 hyperV servers in my test env, runnning about 45 clients. All 3 are reporting this error at some point throught the day. This often means that I need to restart the service hyperV Virtual Machine manager, and obviouisly during that time the SCVMM server (which is a VM client within these 3) looses contact until the service is restarted.

     

    Log Name:      System
    Source:        Service Control Manager
    Date:          8/13/2008 11:39:38 AM
    Event ID:      7011
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      BMA-HYPERV-02.xxxx.xx

    Description:
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the vmms service.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7011</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-08-13T14:39:38.000Z" />
        <EventRecordID>13345</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>BMA-HYPERV-02.xxxxx.xxx</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">30000</Data>
        <Data Name="param2">vmms</Data>
      </EventData>
    </Event>

     

     

    Log Name:      Application
    Source:        Application Error
    Date:          8/13/2008 11:42:31 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      BMA-HYPERV-02.xxxx.xxx

    Description:
    Faulting application vmms.exe, version 6.0.6001.18016, time stamp 0x484fc22e, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791adec, exception code 0xc0000374, fault offset 0x00000000000a6e97, process id 0x156c, application start time 0x01c8fd528d23eb06.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-08-13T14:42:31.000Z" />
        <EventRecordID>1723</EventRecordID>
        <Channel>Application</Channel>
        <Computer>BMA-HYPERV-02.montpelierre.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data>vmms.exe</Data>
        <Data>6.0.6001.18016</Data>
        <Data>484fc22e</Data>
        <Data>ntdll.dll</Data>
        <Data>6.0.6001.18000</Data>
        <Data>4791adec</Data>
        <Data>c0000374</Data>
        <Data>00000000000a6e97</Data>
        <Data>156c</Data>
        <Data>01c8fd528d23eb06</Data>
      </EventData>
    </Event>

     

Answers

All Replies

  • Thursday, August 14, 2008 7:42 PMclanger7 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I have the same problem with VMM 2008 patched. It makes it hard to complete a migration or new system builds. I have posted a feedback message on the connections site. I will note the response out here.

     

    Faulting application vmms.exe, version 6.0.6001.18016, time stamp 0x484fc22e, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791adec, exception code 0xc0000005, fault offset 0x000000000001e758, process id 0x1140, application start time 0x01c8fe43ec14848f.

     
  • Saturday, August 16, 2008 6:08 PMCarmen SummersOwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Did you gather trace logs for this?  If not, please do so an attach to your connect bug.

     

     
  • Saturday, August 16, 2008 6:08 PMCarmen SummersOwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Gather trace logs and open a bug on connect.microsoft.com.

     
  • Friday, August 22, 2008 6:55 PMDesmond LeeMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Could you provide details on how best to do this?

     

    Thanks.

     
  • Friday, August 22, 2008 7:46 PMTony de Sousa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I have found that if I do not use the same NIC for the server communication as for the HyperV virtual NIC, that I do not get this error and instability of hyperV.

     

    I have gone back and reconfigure all hyperV servers and they all no longer have this issue.

     

    In summay I now have one NIC for server to domain communication. I then configure another NIC or NICs for HyperV virtual NICs. If one of these NICs is on the same network as the server nic, I simply do not register this nic on DNS. I also remove all protocols from these vitual NICs, simply IP.

     

    I am not sure if this is the correct resolution but has helped me.

     

    Tony

     

     
  • Wednesday, December 24, 2008 7:35 PMRichard Dixon Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
     Hello,
    I have the same problem with my Hyper V system as well.  I tried Tony's suggestion, I would say that it did not resolve my problem but I do notice that it delayed the restarting of the service, so it still happens.

    The description of my problem is:

    1. The Hyper V service stops and sometimes i have to restart it and sometimes it restarts on its on.
    2. I get the following errors in Event Viewer:

    Log Name:      Application
    Source:        Application Error
    Date:          12/24/2008 10:19:28 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      server.contoso.com
    Description:
    Faulting application vmms.exe, version 6.0.6001.18125, time stamp 0x48ab767f, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791adec, exception code 0xc0000374, fault offset 0x00000000000a6e97, process id 0x2b80, application start time 0x01c965ec130a8123.
    Event Xml:
    <Event xmlns="    http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-12-24T18:19:28.000Z" />
        <EventRecordID>4849</EventRecordID>
        <Channel>Application</Channel>
        <Computer>server.contoso.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>vmms.exe</Data>
        <Data>6.0.6001.18125</Data>
        <Data>48ab767f</Data>
        <Data>ntdll.dll</Data>
        <Data>6.0.6001.18000</Data>
        <Data>4791adec</Data>
        <Data>c0000374</Data>
        <Data>00000000000a6e97</Data>
        <Data>2b80</Data>
        <Data>01c965ec130a8123</Data>
      </EventData>
    </Event>

    • The following is the error that is generated next after the above error:

    Log Name:      System
    Source:        Service Control Manager
    Date:          12/24/2008 10:19:31 AM
    Event ID:      7031
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      server.contoso.com
    Description:
    The Hyper-V Virtual Machine Management service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.
    Event Xml:
    <Event xmlns="    http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7031</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-12-24T18:19:31.000Z" />
        <EventRecordID>115782</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>server.contoso.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">Hyper-V Virtual Machine Management</Data>
        <Data Name="param2">1</Data>
        <Data Name="param3">120000</Data>
        <Data Name="param4">1</Data>
        <Data Name="param5">Restart the service</Data>
      </EventData>
    </Event>

    • The following is the error that is generated next after the above error: 


    Log Name:      Application
    Source:        Microsoft-Windows-WMI
    Date:          12/24/2008 10:19:35 AM
    Event ID:      5612
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      server.contoso.com
    Description:
    Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: HandleCount  Value: 4620 Maximum value: 4096 WMIPRVSE PID: 6708
    Event Xml:
    <Event xmlns="    http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" EventSourceName="WinMgmt" />
        <EventID Qualifiers="49152">5612</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-12-24T18:19:35.000Z" />
        <EventRecordID>4850</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>server.contoso.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>HandleCount</Data>
        <Data>4620</Data>
        <Data>4096</Data>
        <Data>6708</Data>
      </EventData>
    </Event>

    I only see a few people having this issue, so I imagine that it will be a while finding a solution.


    Sr Systems Engineer at Microsoft
     
  • Wednesday, January 07, 2009 2:13 PMJason A Pearce Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Has Code
    Sign In to Vote
    0
    Sign In to Vote
    Like those above, I also have an unstable Hyper-V server (fully patched as of 7 Jan 2009). This problem started to occur on 29 Nov 2008 and has happened 15 times, normally between 2:30 a.m. and 3:30 a.m. ET (-05:00 GMT).

    In the Sever Manager > Diagnostics > Event Viewer > Custom Views > Administrative Events, this Event 1000 Application Error occurs:

    Log Name:      Application
    Source:        Application Error
    Date:          1/7/2009 3:17:18 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NAPA.ais-site.com
    Description:
    Faulting application vmms.exe, version 6.0.6001.18125, time stamp 0x48ab767f, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791adec, exception code 0xc0000005, fault offset 0x0000000000047960, process id 0x7e4, application start time 0x01c96e440677bbd3.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-01-07T08:17:18.000Z" />
        <EventRecordID>1143</EventRecordID>
        <Channel>Application</Channel>
        <Computer>NAPA.ais-site.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>vmms.exe</Data>
        <Data>6.0.6001.18125</Data>
        <Data>48ab767f</Data>
        <Data>ntdll.dll</Data>
        <Data>6.0.6001.18000</Data>
        <Data>4791adec</Data>
        <Data>c0000005</Data>
        <Data>0000000000047960</Data>
        <Data>7e4</Data>
        <Data>01c96e440677bbd3</Data>
      </EventData>
    </Event>


    Less than 10 seconds after this Event 1000 Application Error occurs, I get the following Event 7031 Service Control Manager Eventlog Provider error:

    Log Name:      System
    Source:        Service Control Manager
    Date:          1/7/2009 3:17:23 AM
    Event ID:      7031
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NAPA.ais-site.com
    Description:
    The Hyper-V Virtual Machine Management service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7031</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-01-07T08:17:23.000Z" />
        <EventRecordID>17410</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>NAPA.ais-site.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">Hyper-V Virtual Machine Management</Data>
        <Data Name="param2">1</Data>
        <Data Name="param3">120000</Data>
        <Data Name="param4">1</Data>
        <Data Name="param5">Restart the service</Data>
      </EventData>
    </Event>


    And twice, right after these two events, the Hyper-V host followed with a reboot of its own, first prompting an Event 6008 EventLog:

    Log Name:      System
    Source:        EventLog
    Date:          1/4/2009 3:10:53 AM
    Event ID:      6008
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NAPA.ais-site.com
    Description:
    The previous system shutdown at 3:08:00 AM on 1/4/2009 was unexpected.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="EventLog" />
        <EventID Qualifiers="32768">6008</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-01-04T08:10:53.000Z" />
        <EventRecordID>17187</EventRecordID>
        <Channel>System</Channel>
        <Computer>NAPA.ais-site.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>3:08:00 AM</Data>
        <Data>1/4/2009</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>1339918</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Binary>D9070100000004000300080000003302D90701000000040008000800000033023C0000003C000000000000000000000000000000000000000100000000000000</Binary>
      </EventData>
    </Event>


    Followed by this Event 1101 Eventlog:

    Log Name:      Security
    Source:        Microsoft-Windows-Eventlog
    Date:          1/4/2009 3:10:54 AM
    Event ID:      1101
    Task Category: Event processing
    Level:         Error
    Keywords:      Audit Success
    User:          N/A
    Computer:      NAPA.ais-site.com
    Description:
    Audit events have been dropped by the transport.  The real time backup file was corrupt due to improper shutdown.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Eventlog" Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
        <EventID>1101</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>101</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4020000000000000</Keywords>
        <TimeCreated SystemTime="2009-01-04T08:10:54.533Z" />
        <EventRecordID>12711</EventRecordID>
        <Correlation />
        <Execution ProcessID="364" ThreadID="1044" />
        <Channel>Security</Channel>
        <Computer>NAPA.ais-site.com</Computer>
        <Security />
      </System>
      <UserData>
        <AuditEventsDropped xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
          <Reason>34</Reason>
        </AuditEventsDropped>
      </UserData>
    </Event>


    Within Event Viewer > Applications and Services Logs > Microsoft > Windows > Hyper-V-Hypervisor I often find an Event 8451 Hyper-V-Hypervisor Error shortly before the service restarts:

    Log Name:      Microsoft-Windows-Hyper-V-Hypervisor-Operational
    Source:        Microsoft-Windows-Hyper-V-Hypervisor
    Date:          1/4/2009 3:11:38 AM
    Event ID:      8451
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      NAPA.ais-site.com
    Description:
    Hyper-V failed creating a new partition (status 11)!
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-Hypervisor" Guid="{52fc89f8-995e-434c-a91e-199986449890}" />
        <EventID>8451</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x2000000000000000</Keywords>
        <TimeCreated SystemTime="2009-01-04T08:11:38.368Z" />
        <EventRecordID>462</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="72" />
        <Channel>Microsoft-Windows-Hyper-V-Hypervisor-Operational</Channel>
        <Computer>NAPA.ais-site.com</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="PartitionId">11</Data>
      </EventData>
    </Event>


    I hope I haven't abused this thread by posting too much information. More so, I hope one of us discovers a resolution that returns our Hyper-V hosts into more stable platforms.
     
  • Monday, January 12, 2009 12:15 AMRichard Dixon Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Sign In to Vote
    0
    Sign In to Vote
    I wanted to add some additional inforamtion i found yet to still find an answer to this. I'm engaging the SCVMM product group on this with hopes to get an answer/resolution to this.

    I captured some debug logs during the failure of this service. The log lines in yellow is the capture from a debug session when the failure happened.

    hopes this helps us get somehere on this.

    00010133             107819.91406250              [5076] 13D4.200C::01/11-23:47:50.424#17:utils.cpp(48)[00000000026BE7: FileVersion: error GetFileVersionInfoSize file: [E:\VM_Bin\Client2\Client2.vhd], 0x80070714

    00010134             107826.84375000              [5076] 13D4.200C::01/11-23:47:57.291#02:sanacceleratorminiprovider.cpp(2658): Volume is on a dynamic disk            

    00010135             107826.84375000              [5076] 13D4.200C::01/11-23:47:57.292#02:sanacceleratorminiprovider.cpp(1687)[0000000000EF50: GetLUNIDFromFSPath: Caught exception. Returning error code 6   

    00010136             107934.58593750              [5076] 13D4.0370::01/11-23:49:44.655#00:genericthreadpool.cpp(402)[000000000102BD: Thread 370 received stop key. Exiting            

    00010137             107934.58593750              [5076] 13D4.0874::01/11-23:49:44.656#00:genericthreadpool.cpp(402)[000000000102BD: Thread 874 received stop key. Exiting            

    00010138             107934.58593750              [5076] 13D4.1480::01/11-23:49:44.655#00:genericthreadpool.cpp(402)[000000000102BD: Thread 1480 received stop key. Exiting         

    00010139             107934.58593750              [5076] 13D4.211C::01/11-23:49:44.655#00:genericthreadpool.cpp(402)[000000000102BD: Thread 211c received stop key. Exiting          

    00010140             107934.58593750              [5076] 13D4.22C0::01/11-23:49:44.656#00:genericthreadpool.cpp(402)[000000000102BD: Thread 22c0 received stop key. Exiting          

    00010141             107938.46093750              [6712] 1A38.21D8::01/11-23:49:48.507#00:timer.cpp(487): CTimerMgr::TimerThread   

    00010142             107938.46093750              [6712] 1A38.21D8::01/11-23:49:48.507#00:timer.cpp(500)[000000000069BA: CTimerMgr::TimerThreadInternal   

    00010143             107938.46093750              [6712] 1A38.117C::01/11-23:49:48.514#02:sanminiprovider.cpp(152): Opening global vds session  

    00010144             107938.47656250              [6712] 1A38.0870::01/11-23:49:48.514#02:sanacceleratorminiprovider.cpp(116): Opening global vds session               

    00010145             107974.60937500              [6556] Error -      

    00010146             107974.60937500              [6556] WerpSetReportingForProcess Invalid args       

    00010147             107974.60937500              [6556]   

    00010148             107974.67968750              [5292] Error -      

    00010149             107974.67968750              [5292] ReadProcessMemory failed while trying to read PebBaseAddress              

    00010150             107974.67968750              [5292]   

    00010151             107974.67968750              [5292] Error -      

    00010152             107974.67968750              [5292] Failed to read the peb from the process           

    00010153             107974.67968750              [5292]   

    00010154             107974.70312500              [5292] Error -      

    00010155             107974.70312500              [5292] ReadProcessMemory failed while trying to read PebBaseAddress              

    00010156             107974.70312500              [5292]   

    00010157             107974.74218750              [5292] Error -      

    00010158             107974.74218750              [5292] ReadProcessMemory failed while trying to read PebBaseAddress              

    00010159             107974.74218750              [5292]   

    00010160             107974.74218750              [5292] Error -      

    00010161             107974.74218750              [5292] Failed to read the peb from the process           

    00010162             107974.74218750              [5292]   

    00010163             107975.78125000              [6376] VSPSTATS: init         

    00010164             107985.50000000              [6712] 1A38.13DC::01/11-23:50:34.483#17:utils.cpp(48)[000000000071E6: FileVersion: error GetFileVersionInfoSize file: [E:\VM_Bin\Client2\Client2.vhd], 0x80070714

    00010165             107985.75000000              [6712] 1A38.13DC::01/11-23:50:34.732#17:utils.cpp(48)[000000000071E6: FileVersion: error GetFileVersionInfoSize file: [E:\VM_Bin\Client2\Client2.vhd], 0x80070714

    00010166             107985.78906250              [6712] 1A38.13DC::01/11-23:50:34.767#00:exceptions.cpp(77)[000000000071D6: CarmineException::CarmineException: CarmineError: 1051488,  hr: 0x80070020             

    00010167             107997.97656250              [5040] VSPSTATS: init         

    00010168             108060.35156250              [6712] 1A38.13DC::01/11-23:51:48.314#02:sanacceleratorminiprovider.cpp(1680)[0000000000F636: LUN has no unique storage identifier   

    00010169             108060.35156250              [6712] 1A38.13DC::01/11-23:51:48.315#02:sanacceleratorminiprovider.cpp(1687)[0000000000F636: GetLUNIDFromFSPath: Caught exception. Returning error code 9   

    00010170             108060.56250000              [6712] 1A38.13DC::01/11-23:51:48.523#02:sanacceleratorminiprovider.cpp(2658): Volume is on a dynamic disk            

    00010171             108060.56250000              [6712] 1A38.13DC::01/11-23:51:48.523#02:sanacceleratorminiprovider.cpp(1687)[0000000000F636: GetLUNIDFromFSPath: Caught exception. Returning error code 6   

    00010172             108062.50000000              [6712] 1A38.13DC::01/11-23:51:50.457#02:sanacceleratorminiprovider.cpp(1680)[0000000000F636: LUN has no unique storage identifier   

    00010173             108062.50000000              [6712] 1A38.13DC::01/11-23:51:50.457#02:sanacceleratorminiprovider.cpp(1687)[0000000000F636: GetLUNIDFromFSPath: Caught exception. Returning error code 9   

    00010174             108063.02343750              [6712] 1A38.13DC::01/11-23:51:50.985#02:sanacceleratorminiprovider.cpp(1680)[0000000000F636: LUN has no unique storage identifier   

    00010175             108063.02343750              [6712] 1A38.13DC::01/11-23:51:50.985#02:sanacceleratorminiprovider.cpp(1687)[0000000000F636: GetLUNIDFromFSPath: Caught exception. Returning error code 9   

    00010176             108063.04687500              [6712] 1A38.13DC::01/11-23:51:51.008#02:sanacceleratorminiprovider.cpp(1687)[0000000000F636: GetLUNIDFromFSPath: Caught exception. Returning error code 13

    00010177             108063.07812500              [6712] 1A38.13DC::01/11-23:51:51.032#02:sanacceleratorminiprovider.cpp(1687)[0000000000F636: GetLUNIDFromFSPath: Caught exception. Returning error code 13

    00010178             108063.09375000              [6712] 1A38.13DC::01/11-23:51:51.054#02:sanacceleratorminiprovider.cpp(1687)[0000000000F636: GetLUNIDFromFSPath: Caught exception. Returning error code 13

    00010179             108063.11718750              [6712] 1A38.13DC::01/11-23:51:51.075#02:sanacceleratorminiprovider.cpp(1687)[0000000000F636: GetLUNIDFromFSPath: Caught exception. Returning error code 13

    00010180             108063.14062500              [6712] 1A38.13DC::01/11-23:51:51.102#02:sanacceleratorminiprovider.cpp(1680)[0000000000F636: LUN has no unique storage identifier   

    00010181             108063.14062500              [6712] 1A38.13DC::01/11-23:51:51.102#02:sanacceleratorminiprovider.cpp(1687)[0000000000F636: GetLUNIDFromFSPath: Caught exception. Returning error code 9   

    00010182             108168.28125000              [6712] 1A38.13DC::01/11-23:53:34.799#17:utils.cpp(48)[000000000071E6: FileVersion: error GetFileVersionInfoSize file: [E:\VM_Bin\Client1\Client1.vhd], 0x80070714

    00010183             108168.35156250              [6712] 1A38.13DC::01/11-23:53:34.872#17:utils.cpp(48)[000000000071E6: FileVersion: error GetFileVersionInfoSize file: [E:\VM_Bin\Client1\Client1.vhd], 0x80070714

    00010184             108168.38281250              [6712] 1A38.13DC::01/11-23:53:34.899#00:exceptions.cpp(77)[000000000071D6: CarmineException::CarmineException: CarmineError: 1051488,  hr: 0x80070020             

    00010185             108176.71093750              [6712] 1A38.13DC::01/11-23:53:43.026#02:sanacceleratorminiprovider.cpp(2658): Volume is on a dynamic disk            

    00010186             108176.71093750              [6712] 1A38.13DC::01/11-23:53:43.027#02:sanacceleratorminiprovider.cpp(1687)[0000000000F636: GetLUNIDFromFSPath: Caught exception. Returning error code 6   

    00010187             108297.02343750              [5040] VSPSTATS: enum    

    00010188             108301.03906250              [8148] VSPSTATS: init         

    00010189             108344.16406250              [6604] Error -      

    00010190             108344.16406250              [6604] WerpSetReportingForProcess Invalid args       

    00010191             108344.16406250              [6604]   

    00010192             108344.21875000              [8284] Error -      

    00010193             108344.21875000              [8284] ReadProcessMemory failed while trying to read PebBaseAddress              

    00010194             108344.21875000              [8284]   

    00010195             108344.21875000              [8284] Error -      

    00010196             108344.21875000              [8284] Failed to read the peb from the process           

    00010197             108344.21875000              [8284]   

    00010198             108344.24218750              [8284] Error -      

    00010199             108344.24218750              [8284] ReadProcessMemory failed while trying to read PebBaseAddress              

    00010200             108344.24218750              [8284]   

    00010201             108344.26562500              [8284] Error -      

    00010202             108344.26562500              [8284] ReadProcessMemory failed while trying to read PebBaseAddress              

    00010203             108344.26562500              [8284]   

    00010204             108344.26562500              [8284] Error -      

    00010205             108344.26562500              [8284] Failed to read the peb from the process           

    00010206             108344.26562500              [8284]   

    00010207             108344.78906250              [9096] VSPSTATS: init         

    00010208             108361.10937500              [3976] Trace Start:0End Index:56   

     

    Richard Dixon MSFT Sr Systems Engineer
    • Proposed As Answer byRichard Dixon Tuesday, January 13, 2009 3:14 AM
    •  
     
  • Tuesday, January 13, 2009 3:18 AMRichard Dixon Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Sign In to Vote
    4
    Sign In to Vote
    Guys, I have a solution for us. I got in contact with the product group and provided this the logs i captuer above for Traces, and it turns out that the issue is a Heap corruption.

    The problem is a known bug and is fixed in Windows 2008 SP2.

    The problem is due to having a virutal machine configured with a SCSI adapter that does not have a drive attached to it. I had virtual machines with this configuration. since removing the un used SCSI adapter, my Hyper V service does not stop and restart.

    So go thru each VM and remove any SCSI adapters that does not have a drive associated with it.

    Hope this helps you guys.

    Thanks
    Richard Dixon MSFT Sr Systems Engineer
     
  • Monday, February 16, 2009 6:44 PMMarkku Mäenpää Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Thanks a million Richard!

    I was very upset as I have a production server which has been in use only for 4 days. I was just getting ready to "hyperventilate" because of this error but now I can breathe easy :-)

    One of my VMs had a SCSI controller but no associated VHD disk for it.

    Markku
     
  • Monday, May 04, 2009 8:31 PMDarwin1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Thanks Richard!  You sorta saved my bacon!  My VM Management Service was crashing every two minutes then recovering, crashing, etc..  Quite harrowing..  The VMs stayed running but I could not figure out why it was happing..  I had one VM out of about 20 on this host that had a SCSI without a VHD attached.  Shut it down, removed it, started it back up and BOOM!  No more crashes... ahhhh...  the sweet smell of victory.  Thanks again Richard for posting this!
    Best regards, Darwin
     
  • Monday, May 11, 2009 2:17 PMbeethoven05 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Has anyone verified that SP2 fixes this issue?
     
  • Tuesday, July 21, 2009 8:17 PMAI-M.Schmidt Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    1
    Sign In to Vote

    I have a 3 node Windows Server 2008 Datacenter Hyper-V cluster running and the reported issue is NOT fixed in SP2!!

    The error occured this evening on a fully patched Windows Server 2008 Hyper-V node (with DPM and VMM agent running)

    error message from the Eventlog:

    Faulting application vmms.exe, Version 6.0.6002.18005, time stamp 0x49e02864, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e0421d, exception code 0xc0000005, fault offset 0x000000000002816e, process id 0x164c, application start time 01ca0a31f54c6dca.

     
  • Monday, August 10, 2009 9:54 AMJoe_ElwayMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    1
    Sign In to Vote
    I can confirm the problem is still present with SP2.  I was doing some test work and set up a VM with a SCSI adapter which I hadn't a chance to attach a disk to yet.  I got a series of crashes of VMMS over the last few days on that production host:

    Faulting application vmms.exe, version 6.0.6001.18125, time stamp 0x48ab767f, faulting module USER32.dll, version 6.0.6001.18000, time stamp 0x4791adc5, exception code 0xc0000005, fault offset 0x000000000001d92e, process id 0x9d8, application start time 0x01ca199f3420bfc2.
     
  • Monday, August 17, 2009 4:58 PMChuck Timon [MSFT]MSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    That is not the correct version for vmms.exe in SP2.
    Chuck Timon Senior, Support Escalation Engineer (SEE) Microsoft Corporation
     
  • Tuesday, September 01, 2009 12:59 AMPaul.W-1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Thanks for the solution Richard!

    I am now running Windows Server 2008 R2, with VMM 2008 R2 (eval) and can confirm that the problem STILL occurs and had no idea why!

    I have since checked the VM's on this server and found the SCSI controller there with no HDD drives attached.
     
  • Friday, November 13, 2009 9:17 AMDavide32 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi Richard,
    How did you capture this debug logs? Is there an advanced debug logging in Hyper-V?

    Thanks a lot,
    Davide

     
  • Friday, January 01, 2010 9:58 PMkbromwich Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    damn

    the scsi controller thing as not worked for me. i have gone through every machine and none of them have scsi controller without a disk attached. I have in fact only 1 machine that is using the scsi controller and that has a disk attached. I am using 2008 r2.
    I thought it maybe that i had a couple of machines that had ide controller with no disk or dvd  attached. i have changed that but still has not fixed the issue

    i am not sure if this is the issue that is causing the host machine to suddenly decide to crash and reboot

     
  • Wednesday, January 06, 2010 9:27 AMsen-sei.eu Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Guys, I have a solution for us. I got in contact with the product group and provided this the logs i captuer above for Traces, and it turns out that the issue is a Heap corruption.

    The problem is a known bug and is fixed in Windows 2008 SP2.

    The problem is due to having a virutal machine configured with a SCSI adapter that does not have a drive attached to it. I had virtual machines with this configuration. since removing the un used SCSI adapter, my Hyper V service does not stop and restart.

    So go thru each VM and remove any SCSI adapters that does not have a drive associated with it.

    Hope this helps you guys.

    Thanks
    Richard Dixon MSFT Sr Systems Engineer

    Hi Guys, if this will work on my machines, on which i have identical problems which by the way are very frustrating, YOU have a nice beer by me. Maybe there is a light in this dark tunnel.
     
  • Sunday, January 24, 2010 5:17 AMsh3p Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I can confirm that this solution helped me.
    VMMS was crashing just about every time I rebooted the host servers, but would eventually start on its own a random amount of time later. Went into all my VMs, removed SCSI adapters where they were not in use, and voila, VMMS hasn't crashed since.

    Thanks!
     
  • Wednesday, February 03, 2010 3:59 PMDanDare3 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Guys

    I'm just an end user, not a techhy, and do not understand the terms used above.

    Yes, I have a list of the following error going back to 2007, Yahoo has been crashing, an immidiatley resetting, every time we tried to print an email from it, also the PC, a domestic PC, was so slow I fionally had to look at the issues.

    I finally have it, the PC, running at an acceptable speed, using HELP, I have gone into advanced tools and found a VERY large error list, as containg the error referred to here.

    Please, please can someone explain to me, in English, rather than using SCSI/VM etc shorthand what I need to do to clear this.


    Sorry, having reread previous post i realise VM ios a virtual M/c, but where do I go to find if I have this VM on my PC.


    Many many thanks for any advice/help


     <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{cfc18ec0-96b1-4eba-961b-622caee05b0a}" />
      <EventID>200</EventID>
      <Version>1</Version>
      <Level>2</Level>
      <Task>4007</Task>
      <Opcode>40</Opcode>
      <Keywords>0x8000000000010000</Keywords>
      <TimeCreated SystemTime="2010-02-03T11:13:59.208Z" />
      <EventRecordID>960</EventRecordID>
      <Correlation ActivityID="{00000000-9B8C-0001-8732-7E5AC1A4CA01}" />
      <Execution ProcessID="1084" ThreadID="556" />
      <Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
      <Computer>Dad-PC</Computer>
      <Security UserID="S-1-5-19" />
      </System>
    - <EventData>
      <Data Name="ShutdownTsVersion">1</Data>
      <Data Name="ShutdownStartTime">2010-02-03T11:07:32.413Z</Data>
      <Data Name="ShutdownEndTime">2010-02-03T11:09:08.931Z</Data>
      <Data Name="ShutdownTime">96518</Data>
      <Data Name="ShutdownUserSessionTime">14820</Data>
      <Data Name="ShutdownUserPolicyTime">341</Data>
      <Data Name="ShutdownUserProfilesTime">1958</Data>
      <Data Name="ShutdownSystemSessionsTime">63901</Data>
      <Data Name="ShutdownPreShutdownNotificationsTime">38524</Data>
      <Data Name="ShutdownServicesTime">19985</Data>
      <Data Name="ShutdownKernelTime">17796</Data>
      <Data Name="ShutdownRootCauseStepImprovementBits">0</Data>
      <Data Name="ShutdownRootCauseGradualImprovementBits">0</Data>
      <Data Name="ShutdownRootCauseStepDegradationBits">0</Data>
      <Data Name="ShutdownRootCauseGradualDegradationBits">0</Data>
      <Data Name="ShutdownIsDegradation">false</Data>
      <Data Name="ShutdownTimeChange">0</Data>
      </EventData>
      </Event>