Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, August 19, 2008 12:06 AM
I recently rebuilt a server with Windows 2008 Enterprise and the Hyper-V role. I migrated several VMs from the old VS2005 R2 environment. I am now receiving the following errors in the system and application event logs several times a day. I am allowing the server to report the errors to Microsoft. The fact that one of the Hyper-V management services is restarting leaves me more than a little concerned about the system's stablity.
Has anyone seen these errors and have any suggestions on solutions??
Thanks in advance for any help!
Todd
System Event Log:
Log Name: System
Source: Service Control Manager
Date: 8/18/2008 4:03:53 PM
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Server1.domain.local
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="{removed the GUID}" 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-08-18T23:03:53.000Z" />
<EventRecordID>7934</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>Server1.domain.local</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>
Application log:
Log Name: Application
Source: Application Error
Date: 8/18/2008 4:03:50 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Server1.domain.local
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 0xf94, application start time 0x01c9017605710543.
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-18T23:03:50.000Z" />
<EventRecordID>368</EventRecordID>
<Channel>Application</Channel>
<Computer>Server1.domain.local</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>f94</Data>
<Data>01c9017605710543</Data>
</EventData>
</Event>
All replies (4)
Saturday, August 23, 2008 2:43 PM âś…Answered
Mike,
I found the source of the issue but I don't understand why.
One of the VMs I have runs utility apps such as WSUS, Symantec System Center, and Spiceworks (system monitoring via WMI). It turns out everytime the Spiceworks scan ran, it caused the Hyper-V Virtual Machine Management service to terminate unexpectedly. The scheduled scan ran every two hours and mirrored the times of the failures. I verified the behavior by disabling the scheduled scans and running a couple of scans manually. Since disabling the scheduled scans the only failures I've encountered were during the two manual scans. It's been almost 24hrs.
The only WMI related changes I have made to the default Windows 2008 installation was to enable remote Hyper-V management from my Vista SP1 desktop following the instructions in John Howard's blog (http://blogs.technet.com/jhoward/archive/2008/03/28/part-1-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx). The account running the Spiceworks network scan is in the domain security group I used for this configuration.
Does this make sense? I don't understand how this scenario can cause the Management service to terminate.
Thanks,
Todd
Tuesday, August 19, 2008 1:09 PM
I did some additional digging last night and realized the service is terminating every two hours. Wanting to make sure I had a stable system before proceeding, I have not yet installed any other applications (e.g. antivirus or backup) or created any scheduled tasks.
Thanks again for any help,
Todd
Tuesday, August 19, 2008 10:12 PM
Were any changes made to the system between the time that it was stable and the time it started crashing on a regular basis?
How many VM's do you have registered, and what hardware are you running Hyper-V on? This isn't a known issue, so getting as much information would help in diagnosing the issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
Wednesday, August 20, 2008 2:35 PM
Mike,
Thanks for taking the time to reply. I'll try and provide as much detail as I can....
1) The Windows 2008 installation is new as of last weekend and the server has exhibited these issues since I installed the hyper-v role and began monitoring the system after adding the VMs and installing the integration components. I can't however tell you exactly when the issue began since the error only occurs every two hours. I checked the system after initial install, updating (from Microsoft Update), and installing Hyper-V and File Server roles. Once the system looked clean I began migrating the VMs. Would the errors have occurred without the migrated VMs I can't say.
2) Six VMs (DC, Exchange 2003, File Server, WSUS, Monitoring, & Misc) all running Windows 2003 SP2 and all currently available patches. None of VMs very busy. In fact, watching task mgr during "normal" operations, CPU utilization stays below 10%, physical memory shows 4+GB available RAM, and per Resource Monitor disk use averages well below 500KBps.
3) Hardware: Tyan S2932-E motherboard, Single Dual-core Operton processor, 12GB of Kingston RAM (Six 2GB DIMMs), Highpoint 3522 array controller with eight SATA disks (two disk RAID-1 for the OS, five disk RAID-5 for VMs and a hot spare), embedded NICs, embedded video, embedded SATA array controller for two backup drives.
- Latest firmware installed on the motherboard and array controller.
- No device warnings displayed in Device Mgr.
4) All updates available from Microsoft Update have been applied.
Please let me know if I need to provide more information.
Thanks again,
Todd