101
101
information about the VM configuration and runtime events. The log file
102
102
is called <computeroutput><literal>VBox.log</literal></computeroutput>
103
103
and resides in the VM log file folder. Typically this will be a
104
directory like this:<screen>$HOME/.VirtualBox/Machines/{machinename}/Logs</screen>When
105
starting a VM, the configuration file of the last run will be renamed to
106
<computeroutput>.1</computeroutput>, up to
104
directory like this:<screen>$HOME/VirtualBox VMs/{machinename}/Logs</screen></para>
106
<para>When starting a VM, the configuration file of the last run will be
107
renamed to <computeroutput>.1</computeroutput>, up to
107
108
<computeroutput>.3</computeroutput>. Sometimes when there is a problem,
108
109
it is useful to have a look at the logs. Also when requesting support
109
110
for VirtualBox, supplying the corresponding log file is
120
121
(CFGM), detailed information about the host CPU type and supported
121
122
features, whether hardware virtualization is enabled, information about
122
123
VT-x/AMD-V setup, state transitions (creating, running, paused,
123
stopping, etc.), guest BIOS messages, guest Additions messages, device
124
specific log entries and at the end of execution, final guest state and
125
condensed statistics.</para>
124
stopping, etc.), guest BIOS messages, Guest Additions messages,
125
device-specific log entries and, at the end of execution, final guest
126
state and condensed statistics.</para>
127
128
<para>In case of crashes, it is very important to collect <emphasis
128
129
role="bold">crash dumps</emphasis>. This is true for both host and guest
133
134
url="http://www.virtualbox.org/wiki/Core_dump">http://www.virtualbox.org/wiki/Core_dump</ulink>.</para>
134
135
</footnote></para>
137
<para>You can also use <computeroutput>VBoxManage
138
debugvm</computeroutput> to create a dump of a complete virtual machine;
139
see <xref linkend="vboxmanage-debugvm" />.</para>
136
141
<para>For network related problems, it is often helpful to capture a
137
142
trace of network traffic. If the traffic is routed through an adapter on
138
143
the host, it is possible to use Wireshark or a similar tool to capture
144
149
the VirtualBox website<footnote>
146
151
url="http://www.virtualbox.org/wiki/Network_tips">http://www.virtualbox.org/wiki/Network_tips</ulink>.</para>
147
</footnote> for information on enabling this capture. Note that the
148
trace files created by VirtualBox are in .pcap format and can be easily
149
analyzed with Wireshark.</para>
152
</footnote> for information on enabling this capture. The trace files
153
created by VirtualBox are in <computeroutput>.pcap</computeroutput>
154
format and can be easily analyzed with Wireshark.</para>
153
<title>The built-in VM debugger</title>
158
<title id="debugger">The built-in VM debugger</title>
155
160
<para>VirtualBox includes a built-in VM debugger, which advanced users
156
may find useful. This debugger allows the user to examine, and to some
157
extent, control, the VM state.<note>
161
may find useful. This debugger allows for examining and, to some extent,
162
controlling the VM state.<warning>
158
163
<para>Use the VM debugger at your own risk. There is no support for
159
164
it, and the following documentation is only made available for
160
165
advanced users with a very high level of familiarity with the
161
166
x86/AMD64 machine instruction set, as well as detailed knowledge of
162
167
the PC architecture. A degree of familiarity with the internals of
163
the guest OS in question is not required, but may be very
168
the guest OS in question may also be very helpful.</para>
167
171
<para>The VM debugger is available in all regular production versions of
168
172
VirtualBox, but it is disabled by default because the average user will
181
185
<para>The debugger can be enabled in three ways:<itemizedlist>
183
<para>Start the <computeroutput>VirtualBox</computeroutput>
184
process with a <computeroutput>--dbg</computeroutput>,
187
<para>Start the VM directly using <computeroutput>VirtualBox
188
--startvm</computeroutput>, with an additional
189
<computeroutput>--dbg</computeroutput>,
185
190
<computeroutput>--debug</computeroutput>, or
186
191
<computeroutput>--debug-command-line</computeroutput> argument.
187
See the VirtualBox usage help for details. Note that these
188
arguments are only useful when a VM is started immediately, using
189
the <computeroutput>--startvm</computeroutput> argument.</para>
192
See the VirtualBox usage help for details.</para>
406
408
<sect2 id="guestcoreformat">
407
409
<title>VM core format</title>
409
<para>VirtualBox uses the 64-bit ELF format for its VM core files. The
410
VM core file contain the memory and CPU dumps of the VM and can be
411
useful for debugging your guest OS. The 64-bit ELF object format
412
specficiation can be obtained here: <literal><ulink
411
<para>VirtualBox uses the 64-bit ELF format for its VM core files
412
created by <computeroutput>VBoxManage debugvm</computeroutput>; see
413
<xref linkend="vboxmanage-debugvm" />. The VM core file contain the
414
memory and CPU dumps of the VM and can be useful for debugging your
415
guest OS. The 64-bit ELF object format specficiation can be obtained
416
here: <literal><ulink
413
417
url="http://downloads.openwatcom.org/ftp/devel/docs/elf-64-gen.pdf">http://downloads.openwatcom.org/ftp/devel/docs/elf-64-gen.pdf</ulink></literal>.</para>
415
419
<para>The overall layout of the VM core format is as follows:</para>
543
547
commands is possible by setting the value to 1 or by removing the
551
<sect2 id="hostPowerMgmt">
552
<title>Poor performance caused by host power management</title>
554
<para>On some hardware platforms and operating systems, virtualization
555
performance is negatively affected by host CPU power management. The
556
symptoms may be choppy audio in the guest or erratic guest clock
559
<para>Some of the problems may be caused by firmware and/or host
560
operating system bugs. Therefore, updating the firmware and applying
561
operating systems fixes is recommended.</para>
563
<para>For optimal virtualization performance, the C1E power state
564
support in the system's BIOS should be disabled, if such a setting is
565
available (not all systems support the C1E power state). Disabling other
566
power management settings may also improve performance. However, a
567
balance between performance and power consumption must always be
571
<sect2 id="gui2D_grayedout">
572
<title>GUI: 2D Video Acceleration option is grayed out</title>
574
<para>To use 2D Video Acceleration within VirtualBox, your host's video
575
card should support certain OpenGL extensions. On startup, VirtualBox
576
checks for those extensions, and, if the test fails, this option is
577
silently grayed out.</para>
579
<para>To find out why it has failed, you can manually execute the
580
following command:</para>
582
<screen>VBoxTestOGL --log "log_file_name" --test 2D</screen>
584
<para>It will list the required OpenGL extensions one by one and will
585
show you which one failed the test. This usually means that you are
586
running an outdated or misconfigured OpenGL driver on your host. It can
587
also mean that your video chip is lacking required functionality.</para>
663
706
<title>No networking in Windows Vista guests</title>
665
<para>Unfortunately, with Vista, Microsoft dropped support for the
666
virtual AMD PCNet card that we are providing to virtual machines. As a
667
result, after installation, Vista guests initially have no networking.
668
VirtualBox therefore ships a driver for that card with the Windows Guest
669
Additions; see <xref linkend="vista_networking" />.</para>
708
<para>With Windows Vista, Microsoft dropped support for the AMD PCNet
709
card that VirtualBox used to provide as the default virtual network card
710
before version 1.6.0. For Windows Vista guests, VirtualBox now uses an
711
Intel E1000 card by default.</para>
671
<para>Starting with version 1.6.0 VirtualBox can emulate an Intel E1000
672
network device which is supported by Vista without any third-party
713
<para>If, for some reason, you still want to use the AMD card, you need
714
to download the PCNet driver from the AMD website (available for 32-bit
715
Windows only). You can transfer it into the virtual machine using a
716
shared folder, see (see <xref linkend="sharedfolders" />).</para>
682
725
within virtualized guests if possible.</para>
685
<sect2 id="win7_audio">
686
<title>No audio in Windows Vista (64-bit) and Windows 7 guests</title>
688
<para>32-bit Windows 7 does not ship with drivers for our emulated audio
689
hardware (AC'97). However, running Windows Update should solve the
690
problem by getting an appropriate driver for it automatically. After
691
that update followed by a reboot you should have working audio.</para>
693
<para>For the 64-bit versions of Windows Vista and 7 you have to
694
download the Realtek AC'97 drivers to enable audio.</para>
697
url="http://www.realtek.com.tw/downloads">http://www.realtek.com.tw/downloads</ulink>
698
for download instructions.</para>
702
729
<title>Long delays when accessing shared folders</title>
714
741
<para>After doing this change, a reboot of the guest is required.</para>
745
<title>USB tablet coordinates wrong in Windows 98 guests</title>
747
<para>If a Windows 98 VM is configured to use the emulated USB tablet
748
(absolute pointing device), the coordinate translation may be incorrect
749
and the pointer is restricted to the upper left quarter of the guest's
753
<para>The USB HID (Human Interface Device) drivers in Windows 98 are very
754
old and do not handle tablets the same way all more recent operating
755
systems do (Windows 2000 and later, Mac OS X, Solaris). To
756
work around the problem, issue the following command:
759
<para><screen>VBoxManage setextradata "VM name" "VBoxInternal/USB/HidMouse/0/Config/CoordShift" 0</screen></para>
761
<para>To restore the default behavior, remove the key or set its value
767
<title>Windows guests are removed from an Active Directory domain after
768
restoring a snapshot</title>
770
<para>If a Windows guest is a member of an Active Directory domain and
771
the snapshot feature of VirtualBox is used, it could happen it loses
772
this status after you restore an older snapshot.
775
<para>The reason is the automatic machine password changing performed by
776
Windows in regular intervals for security purposes. You can disable
777
this feature by following the instruction of this <ulink
778
url="http://support.microsoft.com/kb/154501">http://support.microsoft.com/kb/154501</ulink>
779
article from Microsoft.
743
810
<para>Most Linux-based guests will fail with AMD Phenoms or
744
811
Barcelona-level Opterons due to a bug in the Linux kernel. Enable the
745
812
I/O-APIC to work around the problem (see <xref
746
linkend="settings-general-advanced" />).</para>
813
linkend="settings-system" />).</para>
749
816
<sect2 id="trouble-linux-buggy">
852
919
(called Remote Desktop Connection), there can be large delays between
853
920
input (moving the mouse over a menu is the most obvious situation) and
854
921
output. This is because this RDP client collects input for a certain
855
time before sending it to the VRDP server built into VirtualBox.</para>
922
time before sending it to the RDP server.</para>
857
924
<para>The interval can be decreased by setting a Windows registry key to
858
925
smaller values than the default of 100. The key does not exist initially
900
967
writes), it does not affect the performance of other applications
901
968
running on the host.</para>
972
<title>Bridged networking adapters missing</title>
974
<para>If no bridged adapters show up in the "Networking" section of the
975
VM settings, this typically means that the bridged networking driver was
976
not installed properly on your host. This could be due to the following
977
reasons: <itemizedlist>
979
<para>The maximum allowed filter count was reached on the host. In
980
this case, the MSI log would mention the
981
<computeroutput>0x8004a029</computeroutput> error code returned on
982
NetFlt network component install:<screen>VBoxNetCfgWinInstallComponent: Install failed, hr (0x8004a029)</screen></para>
984
<para>You can try to increase the maximum filter count in the
985
Windows registry at the following key:<screen>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters</screen>The
986
maximum number allowed is 14. After a reboot, try to re-install
991
<para>The INF cache is corrupt. In this case, the install log
992
(<computeroutput>%windir%\inf\setupapi.log</computeroutput> on XP
993
or <computeroutput>%windir%\inf\setupapi.dev.log</computeroutput>
994
on Vista or later) would typically mention the failure to find a
995
suitable driver package for either the
996
<computeroutput>sun_VBoxNetFlt</computeroutput> or
997
<computeroutput>sun_VBoxNetFltmp</computeroutput> components. The
998
solution then is to uninstall VirtualBox, remove the INF cache
999
(<computeroutput>%windir%\inf\INFCACHE.1</computeroutput>), reboot
1000
and try to re-install VirtualBox</para>
1002
</itemizedlist></para>
1006
<title>Host-only networking adapters cannot be created</title>
1008
<para>If host-only adapter cannot be created (either via the Manager or
1009
VBoxManage), then the INF cache is probably corrupt. In this case, the
1010
install log (<computeroutput>%windir%\inf\setupapi.log</computeroutput>
1011
on XP or <computeroutput>%windir%\inf\setupapi.dev.log</computeroutput>
1012
on Vista or later) would typically mention the failure to find a
1013
suitable driver package for the
1014
<computeroutput>sun_VBoxNetAdp</computeroutput> component. Again, as
1015
with the bridged networking problem described above, the solution is to
1016
uninstall VirtualBox, remove the INF cache
1017
(<computeroutput>%windir%\inf\INFCACHE.1</computeroutput>), reboot and
1018
try to re-install VirtualBox.</para>
912
1029
(<computeroutput>vboxdrv</computeroutput>) refuses to load, i.e. you get
913
1030
an "Error inserting vboxdrv: Invalid argument", check (as root) the
914
1031
output of the <computeroutput>dmesg</computeroutput> command to find out
915
why the load failed. The most common reasons are:</para>
919
<para>With Linux 2.6.19 and higher, the NMI watchdog may be active.
920
Add <computeroutput>nmi_watchdog=0</computeroutput> to the kernel
921
command line (e.g. in your grub configuration) and reboot. With the
922
Debian and Ubuntu installation modules, execute <computeroutput>sudo
923
dpkg-reconfigure virtualbox</computeroutput> again.</para>
927
<para>The kernel disagrees about the version of the gcc used to
928
compile the module. Make sure that you use the same compiler as used
929
to build the kernel.</para>
1032
why the load failed. Most probably the kernel disagrees with the version
1033
of the gcc used to compile the module. Make sure that you use the same
1034
compiler as used to build the kernel.</para>
1072
1175
relies on to retrieve valid information about your host's USB devices.
1073
1176
The rest of this section only applies to those older systems.</para>
1076
<para>The current rdesktop-vrdp implementation does not support
1077
accessing USB devices through the
1078
<computeroutput>sysfs</computeroutput>!</para>
1081
1178
<para>As <computeroutput>usbfs</computeroutput> is a virtual filesystem,
1082
1179
a <computeroutput>chmod</computeroutput> on
1083
1180
<computeroutput>/proc/bus/usb</computeroutput> has no effect. The
added
removed
doc/manual/fr_FR/user_Troubleshooting.xml
