I would first check your NICs' speed and load, the amount of RAM allocated for the migrating VM and than check the hypervisor log files.
On Mon, Oct 12, 2015 at 8:19 PM, Jan-Arve Nygård <jan.arve.nyg...@gmail.com> wrote: > What version are you running? Check if the copy.volume.wait setting is set > to 7200 and increase it. If not you could also check > job.cancel.threshold.minutes and job.expire.minutes. > > -Jan-Arve > > 2015-10-13 0:46 GMT+02:00 Ryan Farrington <rfarring...@remitdata.com>: > > > We are experiencing a failure in cloudstack waiting for an async job > > performing a live migration of a volume to finish. I've copied the > relevant > > log entries below.We acknowledge that the migration will take a few hours > > based on the volume of the data and we are looking for a way to increase > > the timeout of 7200 seconds into something we know we can work with. > > > > > > 2015-10-12 00:19:36,043 DEBUG [o.a.c.s.RemoteHostEndPoint] > > (Job-Executor-62:ctx-802065a9 ctx-bb27a168) Failed to send command, due > to > > Agent:27, com.cloud.exception.OperationTimedoutException: Commands > > 835325398 to Host 27 timed out after 7200 > > > > > > > -- Rafael Weingärtner
