vmware config files?

Hewson · 08-20-2007, 08:45 PM

- vmware server on fedora core 6 -

hello.

I have gotten myself into the vmware wilderness . . .

I made a VMware img. It wouldn't start. I deleted the img and attempted to try my luck again at creating an img. Before I tried to create another img. I tried to restart the vmware server, but the server complained that there were running virtual machines and until they were shutdown the service could not be stopped. Apart from the help option, vmware-cmd w/ any option hangs. I was forced to use 'kill' to stop the vmware img that orginally the vmware server said had never started.

Where should I look to edit the config files for the vmware server so that I can remove references to this now defunct img? (my intuition is that the vmware-cmd is reading some config file that points to the now non-existant vmware img and hanging) Pretty much everything is default.

Is this server so hosed i should re-install? I'm fearful that the vmware uninstall will be partial and leave some file that only further complicate my woes.

-s

SlowCoder · 08-20-2007, 08:54 PM

The config files are located at /etc/vmware

But don't jump the gun ...

use vmrun to determine the status of any machine instances.
'vmrun list' - shows list of running vm's
'vmrun stop <full path to .vmx>' - turns off the vm of choice.

Hewson · 08-21-2007, 01:35 PM

Thanks for the response. vmrun also hangs. =0/

Looking in /var/log/vmware/vmware-serverd.log I see:
Aug 21 11:23:33: app| Cannot create or access directory "~/.vmware".
Aug 21 11:23:33: app| Licensecheck_BuildList: Failed to expand user directory.

Hewson · 08-21-2007, 04:42 PM

I reinstalled vmware. it turns out it wasn't hanging the responses were just taking a long time.

Now that I have reinstalled I've been paying attention to /var/log/vmware/vmware-serverd.log

Below is the log's complaints. Any one have an idea about how to fix these issues?

specifically: "vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF" and anything with "VMDB failure"

Code:

Aug 21 14:15:25: app| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF
Aug 21 14:15:25: app| SP: Deleting user session: 2 username: root
Aug 21 14:15:54: app| Accepted new connection at 40 for thread server (0x9975ae8)
Aug 21 14:15:54: app| IPC version negotiation version: VMServerd returning 2.1 to server
Aug 21 14:15:54: app| IPC vmcontrol-temp version: VMServerd returning 11.4 to server that tried 11.4
Aug 21 14:15:54: app| VMServerd IPC closed the connection with thread server (0x9975ae8)
Aug 21 14:15:54: app| VMServerd: server disconnected.
Aug 21 14:17:05: app| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF
Aug 21 14:17:05: app| SP: Deleting user session: 1 username: root
Aug 21 14:18:23: app| VmsdRegister: Config file has changed: /vmware/Windows XP Professional/Windows XP Professional.vmx
Aug 21 14:21:43: app| Error when reading from snhelper: Error:6:Dictionary problem
Aug 21 14:21:43: app| SNAPSHOT: Unable to load dict from /vmware/Windows XP Professional/Windows XP Professional.vmx.
Aug 21 14:21:43: app| SNAPSHOT: Could not get dictionary for "/vmware/Windows XP Professional/Windows XP Professional.vmx"
Aug 21 14:21:43: app| SNAPSHOT: Failed to build tree from /vmware/Windows XP Professional/Windows XP Professional.vmx: 2
Aug 21 14:21:43: app| VMHSVMLoadSnapshot failed: VMDB failure
Aug 21 14:21:43: app| VMHSVMLoadConfig failed: VMDB failure
Aug 21 14:21:43: app| VMHS: Failed to reload config state for: /vmware/Windows XP Professional/Windows XP Professional.vmx, VMDB failure, (null)
Aug 21 14:22:43: app| VmsdRegister: Config file has changed: /vmware/Windows XP Professional/Windows XP Professional.vmx
Aug 21 14:22:43: app| VMHSVMLoadConfig failed: Message

Hewson · 08-22-2007, 12:23 PM

So I never figured out why those complaints are in the log file, but I did figure out why those VMware commands where taking so long: poorly configured DNS. My sysadmin is under the impression that every time something takes unusually long DNS is involved. Seems silly but for whatever reason EVERYTIME i've seen strange slow down, a little bit of fixing to /etc/resolv.conf usually fixs it.

Cheers!