VMware Player online course

Viewing and Understanding VMware Player Virtual Machine Log Files

Learn how to open VMware Player's Message Log, locate vmware.log, understand rotated logs, and preserve evidence when troubleshooting virtual machines.

VMware Player logs help explain what happens during a virtual machine's startup, operation, warning conditions, and shutdown. A log belongs to an individual virtual machine and is stored on the host system—the physical computer and operating system running VMware Player.

There are two related ways to review this information: the in-application Message Log, which presents warning-oriented information, and detailed plain-text log files stored in the virtual machine's directory.

What VMware Player Logs Are Used For

A virtual machine log records diagnostic information for that VM. The information can include startup configuration, virtual hardware reported during launch, runtime operations, warnings, and shutdown or termination events.

Logs are especially useful when a VM will not start, displays a warning, behaves unexpectedly, or stops during shutdown. Look at entries near the time the problem occurred rather than treating every line as an error. Normal lifecycle activity can appear alongside warnings and diagnostic details.

Message Log versus detailed log files

Log source — How to access it — Information provided — Best use

Message Log — In VMware Player, while the VM is powered on, choose Player > Manage > Message Log — Warning-oriented information in a separate window — Quickly checking visible warnings for the active VM.

vmware.log — Open the file in the VM's host-side directory with a plain-text editor — Detailed startup, configuration, runtime, warning, and shutdown entries — Investigating a current or recent problem in depth.

vmware-0.log through additional numbered rotated logs — Open the retained files in the same VM directory — Earlier generations of detailed diagnostic output — Investigating an older run when the current log no longer covers the incident.

Viewing the Virtual Machine Message Log

  1. Power on the virtual machine. The VM must be running before its Message Log can be accessed.
  2. In VMware Player, open the Player menu.
  3. Choose Manage > Message Log.
  4. Review the information in the separate Message Log window.

The Message Log is intended as a convenient warning view. It does not replace the complete diagnostic output in the files stored with the VM. If the displayed warning does not explain the cause, continue with vmware.log.

For example, if a running VM displays a warning, power on the intended VM, open Player > Manage > Message Log, and check that the messages belong to that VM before interpreting them.

Locating Detailed Logs on the Host

Detailed logs are saved in the host-side virtual machine directory. This is the folder containing the VM's configuration and other files, such as its virtual disk and log files. The directory is determined by the VM's configured storage location.

  1. Identify the storage location configured for the virtual machine.
  2. Browse to that folder with the host operating system's file manager.
  3. Look for vmware.log and files whose names begin with vmware- and end in .log.
  4. Open a copy, or open the original in a text editor without modifying it.

The active detailed log is named vmware.log. For a running VM, it is the current file receiving diagnostic entries. If you recently moved the VM, confirm that you are browsing the VM's current storage location rather than an old copy. The topic Move a Virtual Machine provides related file-location context.

What vmware.log Records

The detailed file is plain text, so a normal text editor is sufficient. Search or scan for entries around the time of the startup attempt, warning, failure, or shutdown.

  • Startup and initialization: actions performed as the VM begins running and settings applied during initialization.
  • Virtual hardware and configuration: details reported while virtual processors, memory, disks, network adapters, and other configured devices are launched.
  • Runtime operations: activity occurring while the guest is running, including operational messages and warnings.
  • Shutdown and termination: events recorded as the VM powers off, stops, or terminates.

Correlate log entries with the time the issue occurred. Record the timestamp, the warning or error text, and nearby entries that provide context. A single line often makes more sense when read with the initialization or operation lines immediately before and after it.

Log Rotation and Retained History

VMware Player retains a limited series of detailed logs. The active file is vmware.log. When logging rolls over, earlier output is retained in numbered files such as vmware-0.log and vmware-1.log.

Six rotated log files are retained in addition to the currently active log. As rotation continues, older data is eventually overwritten. Therefore, repeated startup tests can replace evidence from an earlier attempt.

File name pattern — Role — Relative age

vmware.log — Current active detailed log — Current run or most recent active output.

vmware-0.log — First numbered rotated generation — Earlier than the active file; use its timestamp to establish the exact run.

vmware-1.log — Another rotated generation — Earlier retained output than the current file, generally older than the first rotated generation.

Additional retained numbered logs — Remaining rotated generations, up to the retained limit — Progressively older history; timestamps are more reliable than the number alone.

A rotated log may contain evidence from a prior virtual machine run. This is important when the current vmware.log was created or rolled over after the failure. Compare file timestamps and entries inside the files to identify which file covers the incident.

Practical Troubleshooting Workflow

  1. Prepare and reproduce: Start the VM or reproduce the warning or failure when it is safe to do so. Note the time and what action triggered the problem.
  2. Check the Message Log: With the VM powered on, choose Player > Manage > Message Log and review immediately visible warnings.
  3. Open the current detailed log: Browse to the VM directory on the host and open vmware.log in a plain-text editor.
  4. Match the time: Review entries near the recorded startup attempt or failure time. Include surrounding initialization, operation, and shutdown details.
  5. Check rotated history: If the current file does not cover the event, inspect vmware-0.log, vmware-1.log, and the other retained numbered logs.
  6. Preserve evidence: Copy relevant current and rotated files to another location before further retries.
  7. Prepare an escalation record: Include timestamps, exact warning or error text, relevant surrounding entries, and the VMware Player version.

Common Log-Related Problems

The Message Log option is unavailable or unhelpful

Confirm that the intended virtual machine is powered on. Then reopen the management menu and select its Message Log. If the window shows only a short warning or lacks a clear cause, inspect the detailed vmware.log in the VM directory.

The current log does not contain the incident

Do not assume the event was never recorded. The incident may belong to an earlier run and may now be in vmware-0.log or another numbered file. Compare timestamps and search the rotated logs for the startup or failure time.

Evidence disappears after repeated retries

Stop testing long enough to copy the current log and relevant rotated logs elsewhere. Because only a limited number of rotated files are retained, repeated runs can replace the oldest evidence.

Exam-Relevant Notes

  • The Message Log is the VMware Player interface view for warning information about the active virtual machine.
  • The VM must be powered on before opening its Message Log through Player > Manage > Message Log.
  • vmware.log is the current detailed log associated with a running VM.
  • vmware-0.log and vmware-1.log are examples of rotated logs containing earlier output.
  • Six rotated logs are retained in addition to the active log; older data can eventually be overwritten.
  • Detailed logs are stored in the VM's host-side directory, not in the guest operating system's ordinary files.
  • Use timestamps to correlate log entries with the incident and preserve files before repeating tests.

Related VMware Player Topics