asked on

Vmware Server Determing Guest VM Host

Hi Guys,
We have recently taken over a new client environment to provide support for, and found that we have a number of Virtual machines on the network, but for some of these VM's we cannot locate which host they are running on.

Do you know if there are any config files or logs etc that I can check for VMWare Server to let me know what host a particular VM is running on?

all we know is that these servers are Virtual Machines we just dont know where! :)

thanks

dan

JT92677

Scan for "VMWARE.LOG" and look for the string HOSTNAME=

This will give you the name of the machine running the client.

HOSTNAME is the 2nd line in the file.

another string of interest in that file has the string "config file:" that says where the VM resides.,

Both of these strings are prefixed with date and time and VMX:

Hope this is a good start.

Jeff

ahmad2121

you cannot do it from the virtual machine, you must connect to the hypervisor application/server and check it from there.

You need to get the VIclient, which you can download from the hypervisor IP/hostname.

KiandraSS

ASKER

Hi Jeff,
Thanks for your quick reply, this is a VMware Server not an ESX Host though. The issue we don't know which server is hosting this virtual machine? nor where the VM files are located which is what we are trying to work out?

cheers

dan

ahmad2121

if it is a server, if you do a tracert from the computer to a website, it should go through the nic of the host.

KiandraSS

ASKER

Hi Jeff,
They are using ASA devices on the perimeter which is blocking trace route's to web only internal, only get single hops to internal IP's.

thanks

dan

ASKER CERTIFIED SOLUTION

ahmad2121

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

JT92677

Heh Ahmad, I'm Jeff ;-)

And I am baffled by this problem, so was hoping someone actually had a solution, but I see your "solution" was accepted -- so my question is, what was your solution anyway?

<<grin>>

KiandraSS

ASKER

We determined what version of vmware tools were running which came back with 3.5 update 2 which is ESX so the servers must be managed by a VC/ESX somewhere. Due to time constraints we have had to go back to previous support providers for the client to try and find out the information that way.

hopefully they come back to us.

cheers for your efforts

thanks

dan