Solved

Unmigratable VMs because host containing the VM is not reachable


Anyone know why that would be? The hosts are definitely up and it can talk to some hosts in my environment but not others.
icon

Best answer by BSH 9 October 2018, 14:10

@aluciani , @sachindtorne

I was able to solve this issue by going into the xtract VM and adding the vsphere IP addresses to the host file and then refreshing in xtract.

The file is located in /etc/hosts so to edit it you could do

sudo vim /etc/hosts

Then enter the following

.

so

169.192.1.1 . vspherehost.domain.local

Hope that helps!

View original

6 replies

Userlevel 7
Badge +35
Interesting? Can you provide any more details about your environment @BSH ? Thanks
Hello Team,

I am also facing same issue on all vms. Please help to resolve this issue .
Userlevel 7
Badge +35
Hi @BSH

You ale to share some more details about the issue?
@aluciani , @sachindtorne

I was able to solve this issue by going into the xtract VM and adding the vsphere IP addresses to the host file and then refreshing in xtract.

The file is located in /etc/hosts so to edit it you could do

sudo vim /etc/hosts

Then enter the following

.

so

169.192.1.1 . vspherehost.domain.local

Hope that helps!
Userlevel 7
Badge +35
Thanks for sharing and helping others in the community @BSH 👍
I had the same issue. In addition to adding the vsphere FQDN I also had to add each ESX host, b/c they were in vSphere by FQDN.
The issue only arose when I tried to migrate the primary DNS server while powered off.
Think that xtract may only use a single DNS entry for name resolution.
As soon as I added the ESX hosts to the hosts file all VMs immediately became available for migration.

Reply