When contacting VMware with a question or problem, please have the following information available:

• VMware application revision number
• base CPU and hardware configuration
• make and version of the host OS
• Linux kernel version if applicable
• video card and motherboard information if possible
• configuration of your VM (a copy of the configuration file)
• make and version of the guest OS
• sequence of events leading up to the problem
• log files

Following are some of the more common errors with reasons for the error message and possible actions to take to resolve them.

No Operating System Found

No bootable floppy disk or CD-ROM was found.

Other VMs are running. Some devices may be unreachable.

Not an error. Simply warns that because multiple VMs are running concurrently, the current VM may not be able to access a particular device such as a floppy or CDROM, because another VM is accessing it. To guarantee access, you may need to power off one or more VMs.

High resolution timing not available (/dev/rtc: Device or resource busy).

Not an error. High resolution timing is only available to the first VM powered on. If you require high resolution timing for the current VM, you can power off any VM that was started before the current one.

Monitor file /usr/local/vmm does not exist

The VMware System Directory is not in the expected location (/usr/local/lib/vmware). This message typically appears if you selected a different location for the system directory but did not change that location during configuration for this VM.