VMware GSX Server 2.5.2Features | Documentation | Knowledge Base | Discussion Forums You may find the following technical support resources useful in addition to the web documentation. VMware's Knowledge Base is another good place to look for answers to questions for and issues with GSX Server. Go to www.vmware.com/support/kb/enduser/std_alp.php. The VMware newsgroups are primarily forums for users to help each other. You are encouraged to read and post issues, workarounds and fixes. While VMware personnel may read and post to the newsgroups, they are not a channel for official support. The VMware NNTP news server is at news.vmware.com. For a listing of all current newsgroups and the topic areas they cover, see www.vmware.com/support/newsgroups.html. If you have problems while running GSX Server, please report them to the VMware support team. These guidelines describe the information we need from you to diagnose problems. This information largely comes from various log files. Which log file we need depends upon the problem you encounter. Be sure to register your serial number. You may then report your problems by submitting a support request at www.vmware.com/requestsupport. If a virtual machine exits abnormally or crashes, please save the log file before you launch another virtual machine. The key log file to save is the VMware log file for the affected virtual machine. On a Windows host, the vmware.log file in the same directory as the configuration file (.vmx) of the virtual machine that had problems. On a Linux host, the <vmname>.log file in the same directory as the configuration file (.cfg) of the virtual machine that had problems. Also save any core files (core or vmware-core). Provide these to VMware along with any other information that might help us to reproduce the problem. The virtual machine's event log, some of which can be viewed in the VMware Management Interface, is stored as a file on the host. This file can also be useful in the event a virtual machine crashes. On a Windows host, the file is stored in C:\Program Files\VMware\VMware GSX Server\vmserverdRoot\eventlog. Each virtual machine on the host includes an event log file, called event-<path_to_configuration_file>.vmx.log. On a Linux host, the log is called event-<path_to_configuration_file>.cfg.log and is stored in /var/log/vmware. The VMware Management Interface keeps a log. If you encounter problems with the management interface, submit this log file along with your support request. On a Windows host, the log is called mui.log and is stored in C:\Program Files\VMware\VMware Management Interface. On a Linux host, the log is called error_log and is stored in /home/vmware/mui/apache/logs. You can enable logging for the VMware Authorization Service manually. If you encounter problems while connecting remotely to a virtual machine on a GSX Server for Windows host, submit this log file along with your support request.
This enables logging and creates a log file called authd.log. The VMware Registration Service keeps a log. If you encounter problems while connecting to virtual machines or using the management interface, submit this log file along with your support request. On a Windows host, the log is called vmware-serverd-SYSTEM-<PID>.log and is stored in C:\Windows\Temp on a Windows Server 2003 or Windows 2000 host. On a Windows NT host, the file is located in C:\Temp. On a Linux host, the log is called vmware-serverd-<username>-<PID>.log and is stored in /tmp. If you are reporting a problem you encountered while installing GSX Server, it is helpful to submit your installation log file. On a Windows host, the file is VMInst.log. It is saved in your temp folder. On a Windows Server 2003 or Windows 2000 host, the default location is C:\Documents and Settings\<username>\Local Settings\Temp. The Local Settings folder is hidden by default. To see its contents, open My Computer, go to Tools > Folder Options, click the View tab and select Show Hidden Files and Folders. On a Windows NT host, the default location is C:\Temp. On a Linux host, the log is called locations and is stored in /etc/vmware. |
