27 Feb
2014
27 Feb
'14
8:38 a.m.
On Thu, Feb 27, 2014 at 10:42:54AM +0100, Koen Vanoppen wrote:
Sorry... I added the correct one now
Still, I fail to find the relevant ::ERROR:: line about migration. But as Michal mentioned, "Could not connect to peer VDS" means that source vdsm failed to contact the destination one. This can stem from physical or logical network problem. Can you ping from source to dest? Can what happens when you log into source host and run vdsClient -s fqdn-of-destination-host list ? do you get any response? What happens if you disable your firewall? Regards, Dan.