| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="collect-debug-info">
|
|---|
| 4 | <title>Collecting Debugging Information</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | For problem determination, it is often important to collect
|
|---|
| 9 | debugging information which can be analyzed by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
|
|---|
| 10 | support. This section contains information about what kind of
|
|---|
| 11 | information can be obtained.
|
|---|
| 12 | </p>
|
|---|
| 13 | <p>
|
|---|
| 14 | Every time <ph conkeyref="vbox-conkeyref-phrases/product-name"/> starts up a VM, a so-called
|
|---|
| 15 | <i>release log file</i> is created, containing
|
|---|
| 16 | lots of information about the VM configuration and runtime
|
|---|
| 17 | events. The log file is called <filepath>VBox.log</filepath> and
|
|---|
| 18 | resides in the VM log file folder, which is
|
|---|
| 19 | <filepath>$HOME/VirtualBox
|
|---|
| 20 | VMs/<varname>VM-name</varname>/Logs</filepath> by
|
|---|
| 21 | default.
|
|---|
| 22 | </p>
|
|---|
| 23 | <p>
|
|---|
| 24 | When starting a VM, the configuration file of the last run will
|
|---|
| 25 | be renamed to <filepath>.1</filepath>, up to
|
|---|
| 26 | <filepath>.3</filepath>. Sometimes when there is a problem, it
|
|---|
| 27 | is useful to have a look at the logs. Also when requesting
|
|---|
| 28 | support for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, supplying the corresponding log file
|
|---|
| 29 | is mandatory.
|
|---|
| 30 | </p>
|
|---|
| 31 | <p>
|
|---|
| 32 | For convenience, for each virtual machine, <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> can show
|
|---|
| 33 | these logs in a window. Select a virtual machine from the
|
|---|
| 34 | machine list on the left and click
|
|---|
| 35 | <b outputclass="bold">Logs</b> in the machine tools menu.
|
|---|
| 36 | </p>
|
|---|
| 37 | <p>
|
|---|
| 38 | The release log file, <filepath>VBox.log</filepath>, contains a
|
|---|
| 39 | wealth of diagnostic information, such as Host OS type and
|
|---|
| 40 | version, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> version and build. It also includes a
|
|---|
| 41 | complete dump of the guest's configuration (CFGM), detailed
|
|---|
| 42 | information about the host CPU type and supported features,
|
|---|
| 43 | whether hardware virtualization is enabled, information about
|
|---|
| 44 | VT-x/AMD-V setup, state transitions (such as creating, running,
|
|---|
| 45 | paused, stopping), guest BIOS messages, Guest Additions
|
|---|
| 46 | messages, device-specific log entries and, at the end of
|
|---|
| 47 | execution, final guest state and condensed statistics.
|
|---|
| 48 | </p>
|
|---|
| 49 | <p>
|
|---|
| 50 | In case of crashes, it is very important to collect
|
|---|
| 51 | <i>crash dumps</i>. This is true for both host and
|
|---|
| 52 | guest crashes. For information about enabling core dumps on
|
|---|
| 53 | Linux, Oracle Solaris, and macOS systems, refer to the following
|
|---|
| 54 | core dump article on the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> website:
|
|---|
| 55 | </p>
|
|---|
| 56 | <p><ph>http://www.virtualbox.org/wiki/Core_dump</ph>.
|
|---|
| 57 | </p>
|
|---|
| 58 | <p> You can also use <userinput>VBoxManage debugvm</userinput> to create a dump of a complete
|
|---|
| 59 | virtual machine. See <xref href="vboxmanage-debugvm.dita">VBoxManage debugvm</xref>. </p>
|
|---|
| 60 | <p>
|
|---|
| 61 | For network related problems, it is often helpful to capture a
|
|---|
| 62 | trace of network traffic. If the traffic is routed through an
|
|---|
| 63 | adapter on the host, it is possible to use Wireshark or a
|
|---|
| 64 | similar tool to capture the traffic there. However, this often
|
|---|
| 65 | also includes a lot of traffic unrelated to the VM.
|
|---|
| 66 | </p>
|
|---|
| 67 | <p>
|
|---|
| 68 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides an ability to capture network traffic
|
|---|
| 69 | only on a specific VM's network adapter. Refer to the following
|
|---|
| 70 | network tracing article on the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> website for
|
|---|
| 71 | information on enabling this capture:
|
|---|
| 72 | </p>
|
|---|
| 73 | <p><ph>http://www.virtualbox.org/wiki/Network_tips</ph>.
|
|---|
| 74 | </p>
|
|---|
| 75 | <p>
|
|---|
| 76 | The trace files created by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> are in
|
|---|
| 77 | <filepath>.pcap</filepath> format and can be easily analyzed
|
|---|
| 78 | with Wireshark.
|
|---|
| 79 | </p>
|
|---|
| 80 | </body>
|
|---|
| 81 |
|
|---|
| 82 | </topic>
|
|---|
