VMware LOGFILES finden, erstellen und auswerten

[HartmutSchaumburg]

Hallo,

wenn es mal an der einen oder anderen Stelle klemmt und man nach der Ursache am suchen ist, sind folgende Massnahmen sehr hilfreich, da VMware sehr "geschwätzig" ist, und ziemlich viel protokolliert.

Die hier angegebenen Schritte muss man im übrigen ausführen, wenn man einen Servicecall eröffnet und die entsprechenden Logfiles mitsenden.

Ich stelle das mal ein, damit jeder in der Lage ist, sich die Informationen zu ziehen, die für eine Problembehebung wichtig sein können. Ich denke, das trägt auch zu einer höheren Trefferquote bei der Fehlersuche bei.

Ich habe allerdings keine Lust, das zu übersetzen, ich denke, damit kommt jeder klar.


Hartmut Schaumburg





Hier liegen die entsprechenden Logfiles, bzw. so erstellt man welche:



Ein Support Script erstellen:

Windows Host

Open a command prompt.
Change to the GSX Server program directory.
C:
cd \Program Files\VMware\VMware GSX Server
If you did not install the program in the default directory, use the appropriate drive letter and substitute the appropriate path in the cd command above.
Run the support script. (Nachstehenden Befehl in der DOS-Box eingeben)
cscript vm-support.vbs
After the script runs, it displays the name of the directory where it has stored its output.


Linux Host

Open a terminal.
Run the support script as the user who is running the virtual machine or as root.
vm-support
If you are not running the script as root, the script displays messages indicating that it cannot collect some information. This is normal. If the VMware support team needs that information, a support representative will ask you to run the script again as root. The script creates a compressed .tgz file in the current directory.




Hier liegen die jeweiligen Log Files



The following log files are generated by GSX Server.


Virtual Machine Log File

If a virtual machine exits abnormally or crashes, please run the support script or save the log file before you launch that virtual machine again. The key log file to save is the VMware log file for the affected virtual machine. On a Windows host, the vmware.log file is in the same directory as the configuration file (.vmx) of the virtual machine that had problems. The path to the log file of the active virtual machine appears in the About dialog box. In a console, choose Help > About VMware GSX Server, and look under Additional information.

On a Linux host, the <vmname>.log file is in the same directory as the configuration file (.vmx) of the virtual machine that had problems.

Also save any core files (core or vmware-core).



Virtual Machine Event Log File

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.
Each virtual machine on the host includes an event log file, called event-<path_to_configuration_file>.vmx.log.

On a Windows host, the log is stored in C:\Program Files\VMware\VMware GSX Server\vmserverdRoot\eventlog.

On a Linux host, the log is stored in /var/log/vmware.


VMware Virtual Machine Console Log File

The VMware Virtual Machine Console keeps a log. If you encounter problems with the VMware Virtual Machine Console on a remote client, check this log file.

On a Windows host, the log is called vmware-<username>-<PID>.log and is stored in the user's TEMP directory; by default, this directory is C:\Documents and Settings\<username>\Local Settings\Temp. The path to this file appears in the About dialog box. In a console, choose Help > About VMware GSX Server, and look under Additional information.

On a Linux host, the log is called ui-<PID>.log and is stored in the user's TEMP directory; by default, this directory is /tmp/vmware-<username>. The path to this file appears in the terminal when you start the console.



VMware Management Interface Log File

The VMware Management Interface keeps a log.

On a Windows host, the log is called mui.log and is stored by default in C:\Program Files\VMware\VMware Management Interface.

On a Linux host, the log is called error_log and is stored by default in /var/log/vmware-mui.



VMware Authorization Service Log File

You can enable logging for the VMware Authorization Service manually (known as vmware-authd on Linux hosts).

In a text editor, open the following file:
On a Windows host, edit config.ini, located in C:\Documents and Settings\All Users\Application Data\VMware\VMware GSX Server.
On a Linux host, edit /etc/vmware/config.
Add the following lines to the file:
vmauthd.logEnabled = TRUE
log.vmauthdFileName = "vmauthd.log"
This creates a file called vmauthd.log. On a Windows host, this file appears by default in C:\Windows\system32 or C:\WINNT\system32; on a Linux host, this file appears by default in /var/log/vmware.

Save and close the configuration file. The log is enabled on a Linux host.
On a Windows host, restart the VMware Authorization Service. Choose Start > Administrative Tools > Services. Right-click the VMware Authorization Service and choose Restart. This enables logging.



VMware Registration Service Log File

The VMware Registration Service keeps a log.

On a Windows host, the log is called vmware-serverd.log and is stored in C:\Windows\Temp.

On a Linux host, the log is called vmware-serverd.log and is stored in /var/log/vmware.



VMware GSX Server and VMware Virtual Machine Console Installation Log Files

GSX Server keeps an installation log file.

On a remote client, the VMware Virtual Machine Console keeps an installation log file.

On a Windows host, the file is VMInst.log. It is saved in your temp folder; 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 Linux host, the log is called locations and is stored in /etc/vmware.


Das sind die essentiellen Log-Files. Zusätzlich werden vom P2V und VirtualCenter ebenfalls Logs erzeugt, das ist aber nicht der Schwerpunkt hier im Forum. Viel Spass beim auswerten.