158
<title id="debugger">The built-in VM debugger</title>
158
<title id="ts_debugger">The built-in VM debugger</title>
160
160
<para>VirtualBox includes a built-in VM debugger, which advanced users
161
161
may find useful. This debugger allows for examining and, to some extent,
307
307
<para><computeroutput>writecore</computeroutput> -- writes a VM
308
core file to disk, refer <xref linkend="guestcoreformat" /></para>
308
core file to disk, refer <xref linkend="ts_guest-core-format" /></para>
310
310
</itemizedlist></para>
405
405
provided can be invaluable.</para>
408
<sect2 id="guestcoreformat">
408
<sect2 id="ts_guest-core-format">
409
409
<title>VM core format</title>
411
411
<para>VirtualBox uses the 64-bit ELF format for its VM core files
544
544
<para>Note that this doesn't affect the flushes performed according to
545
the configuration described in <xref linkend="configPeriodicFlush"
545
the configuration described in <xref linkend="ts_config-periodic-flush"
546
546
xrefstyle="template: %n" />. Restoring the default of ignoring flush
547
547
commands is possible by setting the value to 1 or by removing the
551
<sect2 id="hostPowerMgmt">
551
<sect2 id="ts_host-powermgmt">
552
552
<title>Poor performance caused by host power management</title>
554
554
<para>On some hardware platforms and operating systems, virtualization
568
568
considered.</para>
571
<sect2 id="gui2D_grayedout">
571
<sect2 id="ts_gui-2d-grayed-out">
572
572
<title>GUI: 2D Video Acceleration option is grayed out</title>
574
574
<para>To use 2D Video Acceleration within VirtualBox, your host's video
745
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
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
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
756
work around the problem, issue the following command:
783
<sect2 id="ts_d3d8-d3d9-restore">
784
784
<title>Restoring d3d8.dll and d3d9.dll</title>
786
<para>Extracting d3d8 and d3d9.dll from Windows XP installation CD
786
<para>VirtualBox Guest Additions for Windows prior to 4.1.8 did not properly
787
back up the original d3d8.dll and d3d9.dll system files when selecting
788
and installing the experimental Direct3D support. This process replaces
789
both system files with files from the VirtualBox Guest Additions so that
790
Direct3D calls can be handled correctly. Although this issue was fixed
791
with VirtualBox 4.1.8, there is no way the Windows Guest Additions
792
installer can repair these files.</para>
794
<para>Corruption of these files has no implications in case 3D acceleration
795
is enabled and basic Direct3D support is installed, that is, without WDDM
796
(on Windows Vista or higher) or on older Windows systems like Windows XP.
797
With the basic Direct3D support all Direct3D 8.0 and Direct3D 9.0
798
applications will utilize VirtualBox Direct3D files directly and thus
799
will run as expected.</para>
801
<para>For WDDM Direct3D support however, the originally shipped d3d8.dll and
802
d3d9.dll files are required in order to run Direct3D 8.0
803
and Direct3D 9.0 applications. As a result of the above mentioned system
804
files corruption these applications will not work anymore. See below for
805
a step-by-step guide for restoring the original d3d8.dll and d3d9.dll
806
system files in case the VirtualBox Guest Additions installer warned
807
about those incorrect files or when having trouble running Direct3D
810
<note><para>Starting at Windows 7 the 3D desktop (aka Aero) uses DirectX 10
811
for rendering so that corrupted d3d8.dll and d3d9.dll system files will
812
have no effect on the actual rendering.</para></note>
814
<para>This is why such a detected file corruption is not considered as fatal
815
for the basic Direct3D installation on all supported Windows guests,
816
and for WDDM Direct3D installation on Windows 7 and later guests.</para>
818
<para>Extracting d3d8 and d3d9.dll from a Windows XP installation CD:</para>
887
918
linkend="settings-system" />).</para>
890
<sect2 id="trouble-linux-buggy">
921
<sect2 id="ts_linux-buggy">
891
922
<title>Buggy Linux 2.6 kernel versions</title>
893
924
<para>The following bugs in Linux kernels prevent them from executing
1097
1128
<title>Linux hosts</title>
1099
<sect2 id="linuxkernelmodulefailstoload">
1130
<sect2 id="ts_linux-kernelmodule-fails-to-load">
1100
1131
<title>Linux kernel module refuses to load</title>
1102
1133
<para>If the VirtualBox kernel module
added
removed
doc/manual/en_US/user_Troubleshooting.xml
