DOEACC Forum
An Interactive Plateform For DOEACCians and IT Professionals

Collecting Log Files in VMware

There are several files available that might be requested by the VMware technical support to help resolve your problem. The following describes script processes for generating and collecting some of these files.

Collecting VMkernel Files

If the VMkernel fails, normally an error screen is displayed for a period of time and then the virtual machine reboots.

If you specified a VMware core dump partition when you configured your virtual machine, the VMkernel also generates a core dump and error log.

More serious problems in the VMkernel can freeze the machine without an error screen or core dump.

Collecting VirtualCenter Service Console Files

This script collects and packages all relevant VirtualCenter system and configuration information and VirtualCenter log files. This information can be used to analyze the problem you are encountering.

Run the following script on the service console:
/usr/bin/vm-support

Save the resulting file:
vpx-<date>-<unique-xnumber>.tgz

Collecting Service Log Files

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

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 VirtualCenter.
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 VMware Authorization Service and choose Restart. This enables logging.

Collecting Virtual Center Configuration Information

Enable logging:

Open or create the configuration file:
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\config.ini

Or

C:\Documents and Settings\All Users.WINNT\Application Data\VMware\VMware VirtualCenter\config.ini

Add the following line:
vpxd.logVerbose = "TRUE"

Collecting Virtual Center Settings Information

From the Virtual Center client, open the VMware Virtual Center Settings, Advanced tab.
Select File > VMware Virtual Center Settings. When the dialog box appears, select the advanced tab.

Record the information in the server. Options field. Click OK.

Collecting Virtual Center Log Files

These files are useful when you submit requests to technical support.

Open a command prompt window in the machine running VirtualCenter server.
Change to the directory where VirtualCenter is installed.
For example, the if the default installation directory was used:

cd c:\Program Files\VMware\VMware VirtualCenter\

Run the following command to collect the logs:
cscript vclogs.wsf

For example:

cscript vclogs.wsf /n:all /o:vclog.txt

To view help for the command, type at the script directory:

cscript vclogs.wsf /?

Help content is:

Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

This script collects VMware VirtualCenter server log files to help VMware customer support diagnose your problem.

Usage: vclogs.wsf [/?] [/n:value] [/o:value]

Options:
? : Displays this help
N: Number of log files to collect, default is 10.
Specify 'all' to get all the logs.
O: Output filename, default is VirtualCenterLogs- username-date.txt.

Locate and provide the VirtualCenter log.
The location of the VirtualCenter log is dependent on the platform it is running on as well as the user it is running as.

Generally, the log is in TEMP directory. The TEMP directory for the system user is different on different platforms, but typically it is one of the following:

C:\WINDOWS\Temp (on Windows XP)

C:\WINNT\Temp (on Windows 2000, Windows 2003).

In either of these directory there are files named as follows:

vmware-vpxd-SYSTEM-<process_id>.log

Locate and provide the following log files, vmmsi.log and vminst.log. They are typically located in:
c:\documents and settings\administrator\local settings\temp\

Locate and provide the Event Viewer Log files from the VirtualCenter server.
Log on as a user with VirtualCenter Administrator privileges.
Export the files in the defaul event viewer format with .evt extension.
Place all the required files into a zip file.
Incorporate a timestamp into the zip file name.

 

Collecting GSX Server Files and Logs Using Scripts

The GSX Server log files are generated by GSX Server and are collected by the support script as needed. Since there is no support script on a remote GSX Server client, you need to submit a support request at www.vmware.com/requestsupport for any issues you encounter on a client and include the console's log file or its installation log file.

With GSX Server hosts, you can simplify the process of collecting the needed information by running the support script to collect the appropriate log files and system information. Follow the steps below that apply to your host computer.

Note: The support script runs only on the GSX Server host. If you encounter problems on a remote client, you must supply the log files manually. The two log files you should supply, depending upon the problem you encounter on the client, include the VMware Virtual Machine Console log file and the installation log file. See below for more information about these logs.

 

Running GSX Server Scripts for Windows Hosts

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.
cscript vm-support.vbs

After the script runs, it displays the name of the directory where it has stored its output. Use a file compression utility such as WinZip or PKZIP to zip that directory, then include the zip file with your support request.



New User?Register Here
I forgot my password
IMPORTANT LINKS

Important Links

DOEACC Helpdesk

Download Sample C Language Programs

Interview Questions

Windows XP

Windows Vista

Windows 2000 Server

Windows Server 2003

Redhat Linux

Configure RAID in Linux

SUN Solaris

How To Install Sun Solaris

VMWARE

Microsoft Exchange Server

IBM Lotus Notes

C-Language

Java Script

PHP/MYSQL

c++

Desktops

Laptops

Servers

ThinClients

Printers

Terms Of Service
About Us | Site Map | Privacy Policy | Contact Us | Disclaimer

Best Viewed on 1024*768 Resolution