Environment - Test lab with two Hyper-V Server 2012 systems and one Windows 2012 acting as a file server. I had this all working with the VHDs on a SMB 3 file share and could do migrations from with in the Hyper-V Manager console.
Problem - I am now trying to setup VMM 2012 SP1 on a VM. I have gone through the process of setting this up and registering my two Hyper-V hosts. I can see my existing VMs from within the VMM console. I have setup my SMB 3 share in the Fabric storage section. When I create a new VM I can migrate it with out issue. Every time I try to migrate on of the existing VMs that was there before VMM was setup, the VMM service crashes. I am unable to migrate these VMs from within the VMM console. I can still migrate them from with in the Hyper-V Manager console.
Event Logs (two logs) -
##################################################
Log Name: Application
Source: .NET Runtime
Date: 1/5/2013 8:45:26 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: VirtSysCenter.home.com
Description:
Application: vmmservice.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].SubtaskRun(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
##################################################
Log Name: Application
Source: Application Error
Date: 1/5/2013 8:45:27 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: VirtSysCenter.home.com
Description:
Faulting application name: vmmservice.exe, version: 3.1.6011.0, time stamp: 0x50aaba3f
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007feefb7b534
Faulting process id: 0x2f8
Faulting application start time: 0x01cdebc29d55c143
Faulting application path: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\Bin\vmmservice.exe
Faulting module path: unknown
Report Id: e39f611b-57bb-11e2-93ed-00155d258105
Faulting package full name:
Faulting package-relative application ID:
##################################################
I am still very new to VMM so I have probably left out some information that would help. Let me know what other steps or information I could provide. I have seen issues where people of reported various crashed of the UI etc... I have not found anything that says it was isolated to existing VMs that were already on a SMB 3 file share.
- Edited by Rick Eicher Sunday, January 06, 2013 10:14 PM