Revision history [back]

This is odd. Could you please tell me what branch are you using? Also, if you can paste the full logs from c:\Openstack\Logs\nova-compute.log from both hosts, that would be helpful. Please use pastebin or paste.openstack.org

EDIT:

Sorry for answering so late, my original response didn’t get posted from my phone for some reason.

I tried to reproduce, but couldn’t find any issue. I tried with both Kilo and Liberty branches, both work fine. You didn’t said which branch you were using, but judging by the line numbers in the trace I assumed Kilo.

You posted the logs from both Hyper-V Nodes, but unfortunately there is not much information there. I suspect that this exception is masking the real problem, even so, it is odd that there is no Hyper-V error in the logs.

Given that I can confirm that live-migration works, I suspect that the problem is related to the configuration of the Hyper-V nodes. One thing you can try is to start a migration and immediately after it fails, check to see if there is any error with Event Viewer on both Hyper-V Hosts. You should look under “Application and Services\Microsoft\Windows\Hyper-V VMMS”. Also, please set your log level to debug=true in the nova.conf file on both hosts, that should give us a clearer picture of what is happening.