Article ID: 2790310 - View products that this article applies to.
With System Center 2012 Virtual Machine Manager (VMM 2012) SP1, we now allow multiple migrations to occur and we can specify the maximum number of concurrent migration jobs in the properties of the host. What this means is that if we set the migration value to 2 then the third migration job will be queued until one of the earlier jobs is complete, and by default this job will wait 15 minutes before it times out and fails the job.
When this happens you will see errors similar to the following in the VMM Admin Console:
A VMM Trace will show events similar to the following:
00005365 9.20626545  0184.0008::06/24-23:57:57.717 04VirVMTask.cs(211): GetFinalResult, got error: 32768 => [Storage migration for 'VMName' was not finished because maximum storage migration limit '2' was reached, please wait for completion of an ongoing migration operation (Virtual machine ID 29FF9E76-1475-48B9-893E-2F98705B3735).]
To work around this, you can increase the timeout between jobs by creating the following registry key and restarting the VMM service:
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2790310 - Last Review: January 23, 2013 - Revision: 7.0