EDIT: I updated the title to clarify that this seems to apply to ANY Generation 2 VM (including a new blank one), not just existing templates.
I'm not entirely sure what changed. We have a variety of templates defined for different operating systems. It seems that suddenly none of the ones based on Windows Server 2012 R2 will deploy. Other templates (such as Server 2008 R2, Linux) will deploy fine.
It starts the process, copies over the VHDs, etc, and I believe at sometime around sysprep, it errors out:
Error (20413)
VMM encountered a critical exception and created an exception report at C:\ProgramData\VMMLogs\SCVMM.a6d3767d-0673-440d-91ab-7eabfcac1b7d\report.txt.
We are on Update Rollup 9. EDIT: Just upgraded to UR 10 - same problem occurs.
The same error occurs whether we deploy from the VMM Admin Console or the Self Service Portal.
Looking at the referenced file, it shows:
----------------------------------------------------
------------ exceptionObject.ToString() ------------
----------------------------------------------------
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Carmine.HyperVImplementation.WinBlue.VirVMComputerSystem.GetBootTypeAndValue(Msvm_BootSourceSettingData bssd, BootSourceSubType& bootDeviceSubType, String& bootDeviceValue)
at Microsoft.VirtualManager.Engine.VmOperations.NewVmSubtaskBase.RunNewVmSubtasks()
at Microsoft.VirtualManager.Engine.VmOperations.NewVmSubtaskBase.RunSubtask()
at Microsoft.VirtualManager.Engine.VmOperations.NewVmFromTemplateSubtask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.VmOperations.NewCloudVmSubtask.RunNewVmSubtask(NewVmSubtaskBase newVmChildSubtaskToRun)
at Microsoft.VirtualManager.Engine.VmOperations.NewCloudVmSubtask.NewVmFromTemplateAndConfig()
at Microsoft.VirtualManager.Engine.VmOperations.NewCloudVmSubtask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
If this was just affecting one template, I would assume we had somehow changed it and broke it. However, since it is affecting multiple different Server 2012 R2 templates, I feel like something is wrong at a different level. Any ideas?