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