I recently got the following error message in VMM 2012 R2 doing a live migration which I had never seen before in our VMM Hyper-V environment.
VMM cannot complete the host operation on the VM01.domain.com server because of the error:
Virtual machine migration operation for 'VM01' failed at migration source 'HOST21'.
(Virtual machine ID 6DD5F4D2-48F1-4B8A-803B-5275981EF995)
The Virtual Machine Management Service
failed to establish a connection for a Virtual Machine migration with host 'HOST41.domain.com':
The credentials supplied to the package were not recognized (0x8009030D).
Failed to authenticate the connection at the source host: no suitable credentials available.
Unknown error (0x8000)
Resolve the host issue and then try the operation again.
A quick research on the web brought up articles saying Kerberos should be used as authentication protocol for live migrations between Hyper-V Cluster. However, I had done many live migration between hosts before with out getting this error.
Then I found following post: http://vniklas.djungeln.se/2014/10/17/live-migrating-vms-between-clusters-in-vmm-2012-r2/ There Niklas Akerlund points to the VMM Host Access setting and the missing Run As Account for host management. This was exactly the issue I was experiencing.
I used following PowerShell to see the Run As Account of the hosts in a Hyper-V cluster:
Get-SCVMHostCluster -name Cluster2 | Get-SCVMHost | select name, runasaccount
On the cluster node where the Run As Account was missing, I run the PowerShell from Niklas post:
$runas = Get-SCRunAsAccount "SCVMM Admin"
$clu = Get-SCVMHostCluster -Name HYPCLU
Set-SCVMHostCluster -VMHostCluster $clu -VMHostManagementCredential $runas
After that, Shared-Nothing Live Migration from that specific cluster node was working again. Even with CredSSP as authentication protocol.