Hi Mike, Can you check if the agent has debug logging enabled in log4j.xml? If not, this enables it: sed -i 's/INFO/DEBUG/g' /etc/cloudstack/agent/log4j-cloud.xml
Restart agent, then try again and we should see more logs. Regards, Remi Sent from my iPhone > On 07 May 2015, at 22:30, Mike C <mcrosson_cloudst...@nusku.net> wrote: > >> On 2015-05-07 16:23, Daan Hoogland wrote: >> To bad the agent didn't log a stack trace because the ms stacktrace is >> really only telling us that the agent failed to do the migration. > > Yeah, the following is what I have on the agent. There are a number of > records as I've tried doing the migration more than a few times. > > 2015-05-07 14:51:50,183 INFO [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-2:null) Migration thread for r-93-VM is done > 2015-05-07 14:54:01,921 INFO [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-3:null) Live migration of instance r-93-VM initiated > 2015-05-07 14:54:02,222 INFO [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-3:null) Migration thread for r-93-VM is done > 2015-05-07 16:02:16,208 INFO [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-4:null) Live migration of instance r-93-VM initiated > 2015-05-07 16:02:16,510 INFO [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-4:null) Migration thread for r-93-VM is done
