I am not familiar with the deployment model on the kvm agent but there must be a way to up the logging level. I am looking for the message in the 4.4.3 source now (long search). If the deployment model is anything like the ms you should be editing some cloud log4j.xml under /etc. You may have to restart the agent. I am just starting my hack into the kvm corner of things so I am sure there are beter experts to be found on this list or dev@.. But if your patient I'll get there.
Op do 7 mei 2015 om 22:29 schreef Mike C <mcrosson_cloudst...@nusku.net>: > 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 >
