VirtualBox

Changes between Initial Version and Version 1 of VBoxMainLogging


Ignore:
Timestamp:
11/29/12 13:50:02 (17 months ago)
Author:
michael
Comment:

VBoxMainLogging

Legend:

Unmodified
Added
Removed
Modified
  • VBoxMainLogging

    v1 v1  
     1This page contains instructions on debugging the VBoxSVC (server) and Qt GUI frontend activities. In particular, these instructions enable logging of COM components of the so-called VirtualBox Main API. This logging may be helpful when debugging general application problems such as VirtualBox startup errors, VM Selector GUI crashes and so on. For general information about VirtualBox logging, see [wiki:VBoxLogging]. 
     2 
     3A debug build of VirtualBox is required for the debug logging. Once you've got the debug build, make sure there are no running instances of the VBoxSVC process and any VirtualBox frontends. Then, set the environment variables as shown below if you are on a Linux host: 
     4 
     5{{{ 
     6export VBOX_LOG=main.e.l.f+gui.e.l.f 
     7export VBOX_LOG_FLAGS="time tid thread" 
     8export VBOX_LOG_DEST=dir=/path/to/all/logs 
     9}}} 
     10 
     11or as shown below if you are on a Windows host: 
     12 
     13{{{ 
     14set VBOX_LOG=main.e.l.f+gui.e.l.f 
     15set VBOX_LOG_FLAGS=time tid thread 
     16set VBOX_LOG_DEST=dir=D:\path\to\all\logs 
     17}}} 
     18 
     19Now you may start any VirtualBox client from the given environment and it will log into the specified directory. Note that the VBoxSVC process and all processes it starts will inherit the environment of the first client including the debug variables. 

www.oracle.com
ContactPrivacy policyTerms of Use