Finding the folder save log for action clone or migrate server

[Engsys_SP]

I need to convert server between two hosts on Vcenter, i have been connnected them to vcenter with different folder. 

After shutdown server, i proceeding setup clone (migrate) server, but i awlays recevice the notify "connot connect to host"  Tasks function in tabs Monitor.  This notify not show detail why it's cannot connect to host.

I hope I will get everyone's help with some of the following questions.

1. Where should I look for detailed log information?

2. I searched the following path /var/log/vmware but I couldn't find any details about why I got this log.

[Arnout_Verbeken]

You tag "SimpliVity".
Is ths a question about Simplivity Vmware, Simplivity VME, or VME in general?

You post this question in the VME forum, so I am a little bit confused.

[Sanika]

Acccording to standard VMware vSphere environments, specifically vCenter Server and ESXi hosts, this error "Cannot connect to host" might be because of DNS or IP conflicts, vCenter permissions, host compatibility and also need to check network reachability.

vCenter and ESXi log different parts of the process, so depending on where the failure occurs, you’ll want to check both:

vCenter Server Logs: These are useful if the issue is related to vCenter orchestration or permissions. You may look for:
vpxd.log – Main vCenter service log
vpxd-profiler.log – Performance and task profiling
vpxd-alert.log – Alerts and warnings

For eg:
grep -i "clone" /var/log/vmware/vpxd/vpxd.log
or
grep -i "migrate" /var/log/vmware/vpxd/vpxd.log

ESXi Host Logs: If the error is happening during host-to-host communication, you may look for:
vmkernel.log – VM operations, storage, and networking
Location: /var/log/vmkernel.log
hostd.log – Host management service
Location: /var/log/hostd.log
vpxa.log – vCenter agent on ESXi
Location: /var/log/vpxa.log

You may not find any details in /var/log/vmware because the specific logs you're looking for might be located in subdirectories as mentioned above or logs may not be configured to be generated at that location. To fix this, you should specify a more precise path for the log file mentioned above or increase the logging level for vCenter Server.

Hope this helps.

Regards,
Sanika.

If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.