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="guestadd-3d">
|
---|
4 | <title>Hardware 3D Acceleration (OpenGL and Direct3D 8/9)</title>
|
---|
5 |
|
---|
6 | <body>
|
---|
7 | <p>
|
---|
8 | The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions contain experimental hardware
|
---|
9 | 3D support for Windows, Linux, and Oracle Solaris guests.
|
---|
10 | </p>
|
---|
11 | <p>
|
---|
12 | With this feature, if an application inside your virtual machine
|
---|
13 | uses 3D features through the OpenGL or Direct3D 8/9 programming
|
---|
14 | interfaces, instead of emulating them in software, which would
|
---|
15 | be slow, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will attempt to use your host's 3D
|
---|
16 | hardware. This works for all supported host platforms, provided
|
---|
17 | that your host operating system can make use of your accelerated
|
---|
18 | 3D hardware in the first place.
|
---|
19 | </p>
|
---|
20 | <p>
|
---|
21 | The 3D acceleration feature currently has the following
|
---|
22 | preconditions:
|
---|
23 | </p>
|
---|
24 | <ul>
|
---|
25 | <li>
|
---|
26 | <p>
|
---|
27 | It is only available for certain Windows, Linux, and Oracle
|
---|
28 | Solaris guests. In particular:
|
---|
29 | </p>
|
---|
30 | <ul>
|
---|
31 | <li>
|
---|
32 | <p>
|
---|
33 | 3D acceleration with Windows guests requires Windows
|
---|
34 | 2000 or later. Apart from on Windows 2000 guests, both
|
---|
35 | OpenGL and Direct3D 8/9 are supported on an experimental
|
---|
36 | basis.
|
---|
37 | </p>
|
---|
38 | </li>
|
---|
39 | <li>
|
---|
40 | <p>
|
---|
41 | OpenGL on Linux requires kernel 2.6.27 or later, as well
|
---|
42 | as X.org server version 1.5 or later. Ubuntu 10.10 and
|
---|
43 | Fedora 14 have been tested and confirmed as working.
|
---|
44 | </p>
|
---|
45 | </li>
|
---|
46 | <li>
|
---|
47 | <p>
|
---|
48 | OpenGL on Oracle Solaris guests requires X.org server
|
---|
49 | version 1.5 or later.
|
---|
50 | </p>
|
---|
51 | </li>
|
---|
52 | </ul>
|
---|
53 | </li>
|
---|
54 | <li>
|
---|
55 | <p>
|
---|
56 | The Guest Additions must be installed.
|
---|
57 | </p>
|
---|
58 | <note>
|
---|
59 | <p>
|
---|
60 | For the basic Direct3D acceleration to work in a Windows
|
---|
61 | Guest, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to replace Windows system
|
---|
62 | files in the virtual machine. As a result, the Guest
|
---|
63 | Additions installation program offers Direct3D
|
---|
64 | acceleration as an option that must be explicitly enabled.
|
---|
65 | Also, you must install the Guest Additions in Safe Mode.
|
---|
66 | This does <i>not</i> apply to the WDDM
|
---|
67 | Direct3D video driver available for Windows Vista and
|
---|
68 | later. See <xref href="KnownIssues.dita">Known Limitations</xref> for details.
|
---|
69 | </p>
|
---|
70 | </note>
|
---|
71 | </li>
|
---|
72 | <li>
|
---|
73 | <p>
|
---|
74 | Because 3D support is still experimental at this time, it is
|
---|
75 | disabled by default and must be <i>manually
|
---|
76 | enabled</i> in the VM settings. See
|
---|
77 | <xref href="settings-display.dita#settings-display"/>.
|
---|
78 | </p>
|
---|
79 | <note>
|
---|
80 | <p>
|
---|
81 | Untrusted guest systems should not be allowed to use the
|
---|
82 | 3D acceleration features of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, just as
|
---|
83 | untrusted host software should not be allowed to use 3D
|
---|
84 | acceleration. Drivers for 3D hardware are generally too
|
---|
85 | complex to be made properly secure and any software which
|
---|
86 | is allowed to access them may be able to compromise the
|
---|
87 | operating system running them. In addition, enabling 3D
|
---|
88 | acceleration gives the guest direct access to a large body
|
---|
89 | of additional program code in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host
|
---|
90 | process which it might conceivably be able to use to crash
|
---|
91 | the virtual machine.
|
---|
92 | </p>
|
---|
93 | </note>
|
---|
94 | </li>
|
---|
95 | </ul>
|
---|
96 | <p>
|
---|
97 | To enable Aero theme support, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> WDDM video
|
---|
98 | driver must be installed, which is available with the Guest
|
---|
99 | Additions installation. The WDDM driver is not installed by
|
---|
100 | default for Vista and Windows 7 guests and must be
|
---|
101 | <i>manually selected</i> in the Guest Additions
|
---|
102 | installer by clicking <b outputclass="bold">No</b> in the
|
---|
103 | <b outputclass="bold">Would You Like to Install Basic Direct3D
|
---|
104 | Support</b> dialog displayed when the Direct3D feature is
|
---|
105 | selected.
|
---|
106 | </p>
|
---|
107 | <p>
|
---|
108 | The Aero theme is not enabled by default on Windows. See your
|
---|
109 | Windows platform documentation for details of how to enable the
|
---|
110 | Aero theme.
|
---|
111 | </p>
|
---|
112 | <p>
|
---|
113 | Technically, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> implements 3D acceleration by
|
---|
114 | installing an additional hardware 3D driver inside the guest
|
---|
115 | when the Guest Additions are installed. This driver acts as a
|
---|
116 | hardware 3D driver and reports to the guest operating system
|
---|
117 | that the virtual hardware is capable of 3D hardware
|
---|
118 | acceleration. When an application in the guest then requests
|
---|
119 | hardware acceleration through the OpenGL or Direct3D programming
|
---|
120 | interfaces, these are sent to the host through a special
|
---|
121 | communication tunnel implemented by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. The
|
---|
122 | <i>host</i> then performs the requested 3D
|
---|
123 | operation using the host's programming interfaces.
|
---|
124 | </p>
|
---|
125 | </body>
|
---|
126 |
|
---|
127 | </topic>
|
---|