VMware ESXi and vSphere Cluster Management

Viewing Virtual Machine Logs in Oracle VirtualBox

Learn how to open Oracle VirtualBox Log Viewer, read VM warnings and errors, and use diagnostic messages to troubleshoot startup, storage, display, network, and device problems.

Oracle VirtualBox can record diagnostic information for each virtual machine (VM). A VM is a software-defined computer that runs inside VirtualBox, while the host operating system is the physical computer's operating system on which VirtualBox runs.

The Log Viewer is the VirtualBox interface for examining a selected VM's diagnostic log. It helps you investigate warnings, errors, configuration problems, and runtime events from the VirtualBox side of the VM.

What the VirtualBox Log Viewer is used for

Every VM can produce a chronological diagnostic log. Entries commonly describe components starting, devices being attached, settings being applied, warnings being raised, and operations that fail.

A warning signals a potential problem or nonideal condition, but the VM may continue to operate. An error indicates that an operation or component failed. Neither message should be interpreted without considering when it appeared and what the VM was doing at that time.

  • Warnings can reveal fallback behavior, unsupported optional features, or configuration mismatches.
  • Errors can point toward inaccessible storage, failed device attachment, display initialization problems, or missing virtualization support.
  • Normal startup messages provide a baseline for comparison with a failed startup.
  • Recent entries are often the most useful when diagnosing a problem that just occurred.

Prerequisites before opening logs

  1. Open Oracle VirtualBox Manager, the main desktop interface for creating, selecting, configuring, starting, and managing VMs.
  2. Confirm that the intended VM appears in the machine list.
  3. Select that VM in the list.
  4. Start the VM, or attempt the operation that produces the problem, when it is safe to do so.

Log availability and content depend on whether the VM has been run. A machine that has never started may have little or no useful runtime information. Reproducing the issue before opening the log generally makes the newest entries more relevant.

Opening the Log Viewer

With the target VM selected in VirtualBox Manager, use this menu path:

Select the target VM, then use Machine > Show Log.
  1. Select the affected VM in the machine list.
  2. Open the Machine menu.
  3. Choose Show Log, or the equivalent log-display command shown by your version.
  4. Inspect the separate Log Viewer window or panel that opens for the selected VM.

Menu wording and placement can vary slightly between VirtualBox versions. If the command is not visible, first verify that a VM is selected, then inspect the Machine menu for a similarly named log command.

Reading VirtualBox log information

Log entries commonly include a timestamp, the VirtualBox component involved, a status or severity indicator, and a technical message. Start with the newest part of the log and work backward around the time of the failure.

  • Timestamp: Shows when the event occurred. Match it with the time you started the VM or saw the problem.
  • Component: Identifies the area involved, such as storage, networking, display, USB, or virtualization support.
  • Status or severity: Helps distinguish routine information from warnings and errors.
  • Technical message: Describes the condition that VirtualBox observed.

Review entries near the end of the log and around the failure time. Then compare them with messages from a normal startup, if available. A difference between a successful and failed run can reveal which component changed state or produced a new warning.

A log message is evidence for further investigation, not necessarily the direct root cause. For example, a storage error may result from a missing file, an incorrect attachment, a permissions problem, or a preceding configuration issue.

Common VirtualBox log message categories

Storage and optical media
May indicate a missing virtual disk, inaccessible ISO file, invalid optical-media attachment, or storage-controller problem.
Typical next check: Verify that the referenced disk or ISO exists, is readable, and is attached to the expected virtual controller.

Networking
May indicate that a network adapter cannot attach to the selected host interface, bridge, or network mode.
Typical next check: Review the VM's network attachment mode and confirm that the host interface or virtual network is available.

Display and graphics
May indicate video configuration incompatibility, display initialization failure, or a host graphics limitation.
Typical next check: Review display memory, graphics-controller settings, acceleration options, and host graphics compatibility.

Virtualization or hypervisor support
May indicate that hardware virtualization is unavailable, already controlled by another hypervisor, or disabled in firmware.
Typical next check: Confirm host virtualization support and check whether another virtualization layer is using the required feature.

USB and device attachment
May indicate that a USB device, filter, or other virtual device could not be attached.
Typical next check: Confirm that the device is connected, available to the host, and permitted by the VM's device settings.

Example: a VM fails shortly after startup

  1. Start the affected VM or reproduce the startup failure.
  2. Return to VirtualBox Manager and select that VM.
  3. Open Machine > Show Log.
  4. Review the newest messages near the shutdown or failure timestamp.
  5. Look for warnings and errors, paying attention to component names.
  6. Use those component names to decide whether storage, display, networking, or virtualization settings need investigation.

Record the relevant message before changing settings. Keeping the original wording, timestamp, and component name makes later comparison and troubleshooting more reliable.

Example: installation media cannot be used

After attempting to boot the VM, open its Log Viewer and search the newest entries for references to optical media, ISO paths, virtual CD-ROM devices, or storage attachments.

  • Verify that the ISO file still exists at the referenced path.
  • Confirm that the host account running VirtualBox can read the file.
  • Check that the VM's virtual optical drive is enabled and attached to the intended controller.
  • Confirm that the VM is using the expected ISO rather than an outdated or moved file.

Example: unexpected graphics or display warning

  1. Inspect the log generated during VM startup.
  2. Identify entries associated with graphics, display initialization, video configuration, or acceleration.
  3. Compare the warning with the VM's current display settings.
  4. Check host graphics compatibility and change settings only after recording the diagnostic details.

Scope and limitations

The VirtualBox Log Viewer records VirtualBox-side VM activity. It is not the same as the logs maintained by the guest operating system, which is the operating system installed inside the VM.

VirtualBox Log Viewer
Records: Virtual hardware startup, device attachment, VirtualBox warnings, configuration status, and failures at the VM or host-virtualization layer.
Use it when: A VM fails to start, a virtual device cannot attach, or VirtualBox reports a warning or error.

Guest operating system event or journal tools
Records: Applications, services, drivers, system events, and user-level activity inside the guest operating system.
Use it when: The VM starts normally but an application, service, guest driver, or guest operating-system feature fails.

For example, Windows guests may require Event Viewer, while Linux guests may require system journal utilities. If the guest itself is reporting the problem, the VirtualBox log may show that the VM continued running normally and therefore may not contain the application's root cause.

Troubleshooting the Log Viewer

The Log Viewer contains little useful information

  • The VM may not have been started, so there are few runtime entries.
  • The issue may not have been reproduced yet.
  • The failure may have occurred entirely inside the guest operating system.

Start the VM and reproduce the issue if safe. Reopen the VM log and examine the newest entries. If they do not describe the problem, check the guest operating system's event or journal tools.

The log option cannot be found

  • Select the intended VM in VirtualBox Manager before opening the Machine menu.
  • Look for Show Log or an equivalent log-display label.
  • Account for minor menu differences between VirtualBox versions.

A warning appears but the VM still runs

The warning may describe a fallback behavior, an unsupported optional feature, or a noncritical configuration issue. Record the full warning, timestamp, and component. Prioritize a configuration change only when the warning corresponds with observable instability or a VM feature that does not work.

A practical diagnostic workflow

  1. Describe the symptom precisely: failed startup, missing media, display problem, network failure, or device-attachment issue.
  2. Reproduce the symptom and note the time.
  3. Open the selected VM's Log Viewer.
  4. Read the newest entries first, then inspect messages immediately before the failure.
  5. Record warnings, errors, timestamps, component names, and referenced file or device paths.
  6. Check the relevant VM or host configuration without making unnecessary changes.
  7. Compare with a normal startup or an earlier successful run when possible.
  8. Use guest operating-system logs if the VirtualBox log does not explain an issue occurring inside the guest.

Summary

  • Each VM produces diagnostic log output when VirtualBox runs it.
  • Select the VM in VirtualBox Manager before using Machine > Show Log.
  • Inspect timestamps and the newest warnings or errors near the time of failure.
  • Use component names to guide checks of storage, networking, display, virtualization, USB, and other devices.
  • Record log details before changing VM settings.
  • Use guest operating-system tools for problems that occur inside the guest rather than in VirtualBox.

For this topic, continue with the VirtualBox Log Viewer guide whenever you need to review the procedure.