Red Hat Enterprise Virtualization (RHEV) Log Files

Solution Verified - Updated -

Issue

RHEV Logs Overview

RHEV-H logs

Installation

RHEV-H

  • /var/log/ovirt.log
    Contains a complete output of the RHEV-H node installation process.

  • /var/log/vdsm-reg/vdsm-reg.log
    Registration log for vdsm-reg -  a process that registers RHEV-H nodes with the RHEV-M server.

  • /var/log/vdsm-reg/vds_bootstrap_gen.log ****
    Indicates whether the certificates and keys are created for ssl communication with the RHEV-M Server.

  • /var/log/vdsm-reg/vds_bootstrap_complete.log
    A complete RHEV-H installation log, after it has been registered on the RHEV-M.

RHEL

  • /tmp/vds_installer

  • /tmp/vds_bootstrap

VDSM logs

  • /var/vdsm/ (2.2 only)

    • This directory contains all the running VM files, such as .pid, .socket and .stdio.dump. Logs exist only for running VMs.

    • The dump files contains a full stdio and stderr of each running VM. It can be also a good indicator for Spice crashes. StdIO dumps are aggregated into vdsm.log in real time, so that every dump is in the relevant position in the log file.

  • /var/log/vdsm/vdsm.log
    The  vdsm log file reflects all the vdsmd service activity. This is the main system activity log file.

  • /var/log/vdsm/spm-lock.log
    The Storage Pool Manager (SPM)  uses the lease lock algorithm for managing the storage. It works as a regular lock, but time limited. The spm-lock logs this process.

  • /var/log/core
    The core dump files of the KVM and VDSM will be located here.

Linux system logs – sosreport utility

  • The sosreport package can be useful for collecting system dump files and a wide collection of command outputs that will allow a better debugging. RHEV Log Collector is configured to run sosreport and add the output and files produced to the logs archive. To use sosreport:
  1. Type 'sosreport' as root.

  2. Answer a few questions.

  3. Wait till it finishes.

  4. Check your sosreport output (.bz2 on RHEL5 and .xz on RHEL6) at /tmp.

  5. VDSM related command outputs will be placed at /sos_commands/vdsm/ in  the sosreport archive.

  6. The vdsm.log will also be collected to its regular location at /var/log/vdsm/vdsm.log

RHEV-M logs:

Installation

  • %temp%/*RHEVM.log
    Reflects  all RHEV-M installation processes.

Service Activity

  • <install_path>\RHEVManager\Service\log\vdc.log-name
    Reflects  all RHEV-Manager GUI crashes, Active Directory look-ups, Database issues, etc.

  • <install_path>\RHEVManager\Service\log\vdc-history-log.txt
    The log for RHEV-M Data History Collection Service.

  • <install_path>\RHEVManager\NetConsole\logs\NetConsole.log
    This folder holds the Net Console log + messages logging from the hosts  ([hostIP].log).

  • <install_path>\RHEVManager\UserPortal\log\web-log.txt
    Collects all User Portal exceptions.

Guest:

  • Installation  logs are located at <install_path>\RHEV\Tools\InstallLogs\,
    These logs reflect all of the Guest Tools install process.

    • This directory contains log files for each installed component of the RHEV Tools and a log file of the Tools Setup application.
  • <install_path>\RHEV\drivers\Agent\log\RHEV-Agent
    Agent log reflects the conversation between the host and the vm.

    RHEV Agent log level can be raised by adding an environment variable QAGENT_DEBUG = 1 in the Windows Guest settings

  • RHEV-apt service is responsible for updating tools from attached CD (if newer version than installed). It sends its messages to the Event Viewer -> Applications, once it discovers new tools or  fails to install them.

Client:

  • %temp%/spicec.log
    Contains all the Spice Client activity log and indicates all the connection issues.

  • %temp%/usbrdr.log
    Contains USB Redirector logs.

  • C:\users\administrator\AppData\Local\Apps\2.0********\wpfc..xbap****\log
    Contains WPF logs on Windows 7 and 2008 clients.

  • %temp%\${RHEV-M_FQDN}\log.txt or C:\Documents and Settings\[user]\Local Settings\Apps\2.0\[random string]\[random string]\wpfc...xbap_[uuid]\log\log.txt
    Contains WPF logs on Windows XP, Vista and 2003 clients.

Spice Logs:

Can be found here: RHEV: Spice Logs

Log Collector Utility

There is a utility on RHEV-M that collects to one archived file all the system information, logs and database backup.

The created zip file can be opened with 7-zip (yum install p7zip).

How to run Log Collector

On the RHEV-M go to:

          Start->All Programs->Red Hat->RHEV Manager->Log Collector.

Understanding logs

The collected zip file holds all the available logs from the RHEV-M machine, including the db backup file rhevm.bak.

In addition, per each host attached to the system, there is an additional archive file. This file holds the RHEV-H specific logs as listed above. Also it holds sos-reports logs and output of different commands to retrieve full system info.

Time drift:  if RHEV-M and RHEV-H are not synchronized with the same NTP server, there will be some time drift between the timestamps in the logs. To calculate the delta one can use the following:

  • On RHEV-M: the exact date and time (in seconds’ resolution) of the Log Collector start time can be found on the zip file name.

  • On RHEV-H: the exact date can be found on the file “date” located on the rhev-h archive main directory.

The most informative logs are usually vdc-log.txt (on RHEV-M) and vdsm.log, (on RHEV-H/RHEL under /var/log/vdsm) since those reflect the main flow of the application and if any error occurs, it should be monitored first in those logs. (Unless you know the exact component that failed, then you should check the specific log directly).

vdc-log format:

Date-Time [Thread-ID] Severity – Message

example:

22Oct 00:26:41 [1240] INFO  - RegisterVdsCommand::Register(VDS, int, bool) -Updated a  registered VDS - Name: beta-vdsa....com, Hostname: 10.10.10.01, UniqueID: C0C1F842-3F73-B601-79AD-001A647A92AE

vdsm.log format:

[Thread-ID] :: Severity :: Date Time :: component:: line::module::Command.

example:

Thread-1013808::INFO::2009-10-22 22:53:34,517::clientIF::392::vds::create {'bridge': 'rhevm', 'acpiEnable': 'true', 'tabletEn…..

Usage hints:

  • The Date format in vdsm log is YYYY-MM-DD.

  • To trace a specific command in both logs, the command name can be used. Some of the commands have a similar name in both logs.

  • Inside the log, it is useful to track a specific flow by its Thread ID.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.