Last updated on AUGUST 18, 2016
Applies to:Oracle VM VirtualBox - Version 2.x to 5.1 [Release 2.0 to 5.0]
Information in this document applies to any platform.
When troubleshooting technical issues with VirtualBox, it is often important to collect debugging information which can be analyzed by a Service Engineer at Oracle. This document describes the most common form of initial diagnostics, specifically the content and location of the VBox.log file.
Every time VirtualBox starts up a VM, a so-called "release log file" is created containing lots of information about the VM configuration and runtime events. The log file is called VBox.log and resides in the VM log file folder.
The release log file (VBox.log) contains a wealth of diagnostic information, such as Host OS type and version, VirtualBox version and build (32-bit or 64-bit), a complete dump of the guest's configuration (CFGM), detailed information about the host CPU type and supported features, whether hardware virtualization is enabled, information about VT-x/AMD-V setup, state transitions (creating, running, paused, stopping, etc.), guest BIOS messages, Guest Additions messages, device-specific log entries and, at the end of execution, final guest state and condensed statistics.
For convenience, for each virtual machine, the VirtualBox main window can show these logs in a window. To access it, select a virtual machine from the list on the left and select "Show logs..." from the "Machine" window.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms