VirtualBox

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

Last change on this file since 40467 was 40467, checked in by vboxsync, 13 years ago

doc/manual: make documentation of Max OS X support easier to read, and refer to the Apple software license for details, as they change the details relatively frequently

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