VirtualBox

source: vbox/trunk/doc/manual/en_US/user_KnownIssues.xml@ 47471

Last change on this file since 47471 was 46821, checked in by vboxsync, 11 years ago

doc/manual: fixed a few typos

File size: 14.1 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
3"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
4<chapter id="KnownIssues">
5 <title>Known limitations</title>
6 <sect1 id="ExperimentalFeatures">
7 <title>Experimental Features</title>
8 <para>Some VirtualBox features are labeled as experimental. Such
9 features are provided on an "as-is" basis and are not formally
10 supported. However, feedback and suggestions about such features are
11 welcome. A comprehensive list of experimental features follows:</para>
12 <itemizedlist>
13 <listitem>
14 WDDM Direct3D video driver for Windows guests
15 </listitem>
16 <listitem>
17 Hardware 3D acceleration support for Windows, Linux, and Solaris
18 guests
19 </listitem>
20 <listitem>
21 Hardware 2D video playback acceleration support for Windows
22 guests
23 </listitem>
24 <listitem>
25 PCI pass-through (Linux hosts only)
26 </listitem>
27 <listitem>
28 Mac OS X guests (Mac hosts only)
29 </listitem>
30 <listitem>
31 ICH9 chipset emulation
32 </listitem>
33 <listitem>
34 EFI firmware
35 </listitem>
36 <listitem>
37 Host CD/DVD drive pass-through
38 </listitem>
39 <listitem>
40 Support of iSCSI via internal networking
41 </listitem>
42 <listitem>
43 Synthetic CPU reporting
44 </listitem>
45 </itemizedlist>
46 </sect1>
47 <sect1 id="KnownProblems">
48 <title>Known Issues</title>
49 <para>The following section describes known problems with VirtualBox
50 $VBOX_VERSION_STRING. Unless marked otherwise, these issues are planned to
51 be fixed in later releases.</para>
52
53 <itemizedlist>
54 <listitem>
55 <para>The following <emphasis role="bold">Guest SMP (multiprocessor)
56 limitations</emphasis> exist:<itemizedlist>
57 <listitem>
58 <para><emphasis role="bold">Poor performance</emphasis> with
59 32-bit guests on AMD CPUs. This affects mainly Windows and Solaris
60 guests, but possibly also some Linux kernel revisions. Partially
61 solved in 3.0.6 for 32 bits Windows NT, 2000, XP and 2003 guests.
62 Requires 3.0.6 or higher Guest Additions to be installed.</para>
63 </listitem>
64
65 <listitem>
66 <para><emphasis role="bold">Poor performance</emphasis> with
67 32-bit guests on certain Intel CPU models that do not include
68 virtual APIC hardware optimization support. This affects mainly
69 Windows and Solaris guests, but possibly also some Linux kernel
70 revisions. Partially solved in 3.0.12 for 32 bits Windows NT,
71 2000, XP and 2003 guests. Requires 3.0.12 or higher Guest
72 Additions to be installed.</para>
73 </listitem>
74 </itemizedlist></para>
75 </listitem>
76
77 <listitem>
78 <para><emphasis role="bold">64-bit guests on some 32-bit host systems
79 with VT-x</emphasis> can cause instabilities to your system. If you
80 experience this, do not attempt to execute 64-bit guests. Refer to the
81 VirtualBox user forum for additional information.</para>
82 </listitem>
83
84 <listitem>
85 <para><emphasis role="bold">NX (no execute, data execution
86 prevention)</emphasis> only works for guests running on 64-bit hosts
87 or guests running on 32-bit hosts with PAE enabled and requires that
88 hardware virtualization be enabled.</para>
89 </listitem>
90
91 <listitem>
92 <para>For <emphasis role="bold">basic Direct3D support in Windows
93 guests</emphasis> to work, the Guest Additions must be installed in
94 Windows "safe mode". Press F8 when the Windows guest is booting and
95 select "Safe mode", then install the Guest Additions. Otherwise Windows'
96 file protection mechanism will interfere with the replacement DLLs
97 installed by VirtualBox and keep restoring the original Windows system
98 DLLs. <note>
99 <para>This does <emphasis role="bold">not</emphasis> apply to the
100 experimental WDDM Direct3D video
101 driver available for Vista and Windows 7 guests shipped with
102 VirtualBox 4.1.</para>
103 </note></para>
104 </listitem>
105
106 <listitem>
107 <para><emphasis role="bold">Guest control.</emphasis> On Windows guests,
108 a process lauched via the guest control execute support will not be able
109 to display a graphical user interface <emphasis>unless</emphasis> the
110 user account under which it is running is currently logged in and has a
111 desktop session.</para>
112
113 <para>Also, to use accounts without or with an empty password, the
114 guest's group policy must be changed. To do so, open the group policy
115 editor on the command line by typing
116 <computeroutput>gpedit.msc</computeroutput>, open the key
117 <emphasis>Computer Configuration\Windows Settings\Security
118 Settings\Local Policies\Security Options</emphasis> and change the value
119 of <emphasis>Accounts: Limit local account use of blank passwords to
120 console logon only</emphasis> to <emphasis>Disabled</emphasis>.</para>
121 </listitem>
122
123 <listitem>
124 <para><emphasis role="bold">Compacting virtual disk images is limited to
125 VDI files.</emphasis> The <code>VBoxManage modifyhd --compact</code>
126 command is currently only implemented for VDI files. At the moment the
127 only way to optimize the size of a virtual disk images in other formats
128 (VMDK, VHD) is to clone the image and then use the cloned image in the
129 VM configuration.</para>
130 </listitem>
131
132 <listitem>
133 <para><emphasis role="bold">OVF import/export:</emphasis><itemizedlist>
134 <listitem>
135 <para>OVF localization (multiple languages in one OVF file) is not
136 yet supported.</para>
137 </listitem>
138
139 <listitem>
140 <para>Some OVF sections like StartupSection,
141 DeploymentOptionSection and InstallSection are ignored.</para>
142 </listitem>
143
144 <listitem>
145 <para>OVF environment documents, including their property sections
146 and appliance configuration with ISO images, are not yet
147 supported.</para>
148 </listitem>
149
150 <listitem>
151 <para>Remote files via HTTP or other mechanisms are not yet
152 supported.</para>
153 </listitem>
154 </itemizedlist></para>
155 </listitem>
156
157 <listitem>
158 <para>Neither <emphasis role="bold">scale mode</emphasis> nor <emphasis
159 role="bold">seamless mode</emphasis> work correctly with guests using
160 OpenGL 3D features (such as with compiz-enabled window managers).</para>
161 </listitem>
162
163 <listitem>
164 <para>The RDP server in the VirtualBox extension pack supports only
165 audio streams in format 22.05kHz stereo 16 bit. If the RDP client
166 requests any other audio format there will be no audio.</para>
167 </listitem>
168
169 <listitem>
170 <para>Preserving the aspect ratio in scale mode works only on Windows
171 hosts and on Mac OS X hosts.</para>
172 </listitem>
173
174 <listitem>
175 <para>On <emphasis role="bold">Mac OS X hosts,</emphasis> the following
176 features are not yet implemented:</para>
177
178 <para><itemizedlist>
179 <listitem>
180 <para>Numlock emulation</para>
181 </listitem>
182
183 <listitem>
184 <para>CPU frequency metric</para>
185 </listitem>
186
187 <listitem>
188 <para>Memory ballooning</para>
189 </listitem>
190 </itemizedlist></para>
191 </listitem>
192
193 <listitem>
194 <para><emphasis role="bold">Mac OS X guests:</emphasis>
195 <itemizedlist>
196 <listitem>
197 <para>Mac OS X guests can only run on a certain host hardware.
198 For details about license and host hardware limitations, please
199 see <xref linkend="intro-macosxguests" /> and check the Apple
200 software license conditions.</para>
201 </listitem>
202
203 <listitem>
204 <para>VirtualBox does not provide Guest Additions for Mac OS X
205 at this time.</para>
206 </listitem>
207
208 <listitem>
209 <para>The graphics resolution currently defaults to 1024x768 as
210 Mac OS X falls back to the built-in EFI display support. See
211 <xref linkend="efividmode" /> for more information on how to
212 change EFI video modes.</para>
213 </listitem>
214
215 <listitem>
216 <para>Even when idle, Mac OS X guests currently burn 100% CPU.
217 This is a power management issue that will be addressed in a
218 future release.</para>
219 </listitem>
220
221 <listitem>
222 <para>Mac OS X guests only work with one CPU assigned to the
223 VM. Support for SMP will be provided in a future release.</para>
224 </listitem>
225
226 <listitem>
227 <para>Depending on your system and version of Mac OS X, you
228 might experience guest hangs after some time. This can be fixed
229 by turning off energy saving (set timeout to "Never") in the
230 system preferences.</para>
231 </listitem>
232
233 <listitem>
234 <para>By default, the VirtualBox EFI enables debug output of the
235 Mac OS X kernel to help you diagnose boot problems. Note that
236 there is a lot of output and not all errors are fatal (they
237 would also show on your physical Mac). You can turn off these
238 messages by issuing this command:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" " "</screen>To
239 revert to the previous behavior, use:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" ""</screen></para>
240 </listitem>
241 </itemizedlist></para>
242 </listitem>
243
244 <listitem>
245 <para><emphasis role="bold">Solaris hosts:</emphasis> <itemizedlist>
246 <listitem>
247 <para>There is no support for USB devices connected to Solaris 10
248 hosts.</para>
249 </listitem>
250
251 <listitem>
252 <para>USB support on Solaris hosts requires Solaris 11 version
253 snv_124 or higher. Webcams and other isochronous devices are known
254 to have poor performance.</para>
255 </listitem>
256
257 <listitem>
258 <para>No ACPI information (battery status, power source) is
259 reported to the guest.</para>
260 </listitem>
261
262 <listitem>
263 <para>No support for using wireless adapters with bridged
264 networking.</para>
265 </listitem>
266
267 <listitem>
268 <para>Crossbow-based bridged networking on Solaris 11 hosts does
269 not work directly with aggregate links. However, you can manually
270 create a VNIC (using <computeroutput>dladm</computeroutput>) over
271 the aggregate link and use that with a VM. This technical
272 limitation will be addressed in a future Solaris 11 release.</para>
273 </listitem>
274 </itemizedlist></para>
275 </listitem>
276
277 <listitem>
278 <para><emphasis role="bold">Guest Additions of version 4.1, 4.1.2 and 4.1.4 for Windows</emphasis>
279 Thus VirtualBox WDDM Video driver may be installed and kept in guest system
280 if Guest additions uninstallation is performed.
281 This is caused by a bug in Guest Additions uninstaller.
282 <note>
283 <para>This does <emphasis role="bold">not</emphasis> apply to Guest Additions update,
284 i.e. installing a one version of Guest Additions on top of another works correctly.</para>
285 </note>
286 To solve this problem, one should uninstall the VirtualBox WDDM Video driver manually.
287 To do that open Device Manager, and check whether the Display Adapter is named
288 "VirtualBox Graphics Adapter ..". If no - there is nothing to be done. If yes - right-click
289 the VirtualBox Graphics Adapter in Device Manager, select "Uninstall", check "Delete the driver software for this device"
290 and click "OK". Once uninstallation is done - in Device Manager go to menu "Action" and select
291 "Scan for hardware changes" to make the propper (Windows default) driver be picked up for the Graphics adapter.
292 </para>
293 </listitem>
294
295 <listitem>
296 <para>Neither <emphasis>virtio</emphasis> nor <emphasis>Intel PRO/1000
297 </emphasis> drivers for <emphasis role="bold">Windows XP guests
298 </emphasis> support segmentation offloading. Therefore
299 Windows XP guests have slower transmission rates comparing to other
300 guest types. Refer to MS Knowledge base article 842264 for additional
301 information.</para>
302 </listitem>
303
304 <listitem>
305 <para><emphasis role="bold">Guest Additions for OS/2.</emphasis> Shared
306 folders are not yet supported with OS/2 guests. In addition, seamless
307 windows and automatic guest resizing will probably never be implemented
308 due to inherent limitations of the OS/2 graphics system.</para>
309 </listitem>
310 </itemizedlist>
311 </sect1>
312</chapter>
Note: See TracBrowser for help on using the repository browser.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette