VirtualBox

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

最後變更 在這個檔案從34539是 34539,由 vboxsync 提交於 14 年 前

Manual: misc fixes

檔案大小: 9.4 KB
 
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
7 <para>This sections describes known problems with VirtualBox
8 $VBOX_VERSION_STRING. Unless marked otherwise, these issues are planned to
9 be fixed in later releases.</para>
10
11 <itemizedlist>
12 <listitem>
13 <para>The following <emphasis role="bold">Guest SMP (multiprocessor)
14 limitations</emphasis> exist:<itemizedlist>
15 <listitem>
16 <para><emphasis role="bold">Poor performance</emphasis> with
17 32-bit guests on AMD CPUs. This affects mainly Windows and Solaris
18 guests, but possibly also some Linux kernel revisions. Partially
19 solved in 3.0.6 for 32 bits Windows NT, 2000, XP and 2003 guests.
20 Requires 3.0.6 or higher Guest Additions to be installed.</para>
21 </listitem>
22
23 <listitem>
24 <para><emphasis role="bold">Poor performance</emphasis> with
25 32-bit guests on certain Intel CPU models that do not include
26 virtual APIC hardware optimization support. This affects mainly
27 Windows and Solaris guests, but possibly also some Linux kernel
28 revisions. Partially solved in 3.0.12 for 32 bits Windows NT,
29 2000, XP and 2003 guests. Requires 3.0.12 or higher Guest
30 Additions to be installed.</para>
31 </listitem>
32 </itemizedlist></para>
33 </listitem>
34
35 <listitem>
36 <para><emphasis role="bold">64-bit guests on some 32-bit host systems
37 with VT-x</emphasis> can cause instabilities to your system. If you
38 experience this, do not attempt to execute 64-bit guests. Refer to the
39 VirtualBox user forum for additional information.</para>
40 </listitem>
41
42 <listitem>
43 <para>For <emphasis role="bold">Direct3D support in Windows
44 guests</emphasis> to work, the Guest Additions must be installed in
45 Windows "safe mode". Press F8 when the Windows guest is booting and
46 select "Safe mode", then install the Guest Additions. Otherwise Windows'
47 file protection mechanism will interfere with the replacement DLLs
48 installed by VirtualBox and keep restoring the original Windows system
49 DLLs.</para>
50 </listitem>
51
52 <listitem>
53 <para><emphasis role="bold">Guest control.</emphasis> On Windows guests,
54 a process lauched via the guest control execute support will not be able
55 to display a graphical user interface <emphasis>unless</emphasis> the
56 user account under which it is running is currently logged in and has a
57 desktop session.</para>
58
59 <para>Also, to use accounts without or with an empty password, the
60 guest's group policy must be changed. To do so, open the group policy
61 editor on the command line by typing
62 <computeroutput>gpedit.msc</computeroutput>, open the key
63 <emphasis>Computer Configuration\Windows Settings\Security
64 Settings\Local Policies\Security Options</emphasis> and change the value
65 of <emphasis>Accounts: Limit local account use of blank passwords to
66 console logon only</emphasis> to <emphasis>Disabled</emphasis>.</para>
67 </listitem>
68
69 <listitem>
70 <para><emphasis role="bold">Guest multi-monitor support</emphasis> is
71 currently only supported with Windows guests.</para>
72 </listitem>
73
74 <listitem>
75 <para><emphasis role="bold">Disabled host I/O caches.</emphasis>
76 Disabling the host I/O cache (see <xref linkend="iocaching" />) will
77 yield poor performance with VHD and sparse VMDK files as these do not
78 currently support asynchronous I/O. This does not apply to VDI files and
79 raw disk/partition VMDK files, which do support async I/O. This
80 restriction will be lifted in a future maintenance update.</para>
81 </listitem>
82
83 <listitem>
84 <para><emphasis role="bold">Compacting virtual disk images is limited to
85 VDI files.</emphasis> The <code>VBoxManage modifyhd --compact</code>
86 command is currently only implemented for VDI files. At the moment the
87 only way to optimize the size of a virtual disk images in other formats
88 (VMDK, VHD) is to clone the image and then use the cloned image in the
89 VM configuration.</para>
90 </listitem>
91
92 <listitem>
93 <para><emphasis role="bold">OVF import/export:</emphasis><itemizedlist>
94 <listitem>
95 <para>OVF localization (multiple languages in one OVF file) is not
96 yet supported.</para>
97 </listitem>
98
99 <listitem>
100 <para>Some OVF sections like StartupSection,
101 DeploymentOptionSection and InstallSection are ignored.</para>
102 </listitem>
103
104 <listitem>
105 <para>OVF environment documents, including their property sections
106 and appliance configuration with ISO images, are not yet
107 supported.</para>
108 </listitem>
109
110 <listitem>
111 <para>Remote files via HTTP or other mechanisms are not yet
112 supported.</para>
113 </listitem>
114 </itemizedlist></para>
115 </listitem>
116
117 <listitem>
118 <para><emphasis role="bold">Seamless mode</emphasis> does not work
119 correctly with Linux guests that have 3D effects enabled (such as with
120 compiz-enabled window managers).</para>
121 </listitem>
122
123 <listitem>
124 <para><emphasis role="bold">Mac OS X hosts:</emphasis><itemizedlist>
125 <listitem>
126 <para>The numlock emulation has not yet been implemented.</para>
127 </listitem>
128
129 <listitem>
130 <para>The CPU frequency metric is not supported.</para>
131 </listitem>
132
133 <listitem>
134 <para>3D OpenGL acceleration, in particular with Linux guests that
135 have 3D effects enabled (such as with compiz-enabled window
136 managers).</para>
137 </listitem>
138
139 <listitem>
140 <para>Memory ballooning is not supported.</para>
141 </listitem>
142 </itemizedlist></para>
143 </listitem>
144
145 <listitem>
146 <para><emphasis role="bold">Mac OS X Server guests:</emphasis>
147 <itemizedlist>
148 <listitem>
149 <para>Mac OS X Server guests can only run on a certain host
150 hardware. For details about license and host hardware limitations,
151 please see <xref linkend="intro-macosxguests" />.</para>
152 </listitem>
153
154 <listitem>
155 <para>VirtualBox does not provide Guest Additions for Mac OS X
156 Server at this time.</para>
157 </listitem>
158
159 <listitem>
160 <para>The graphics resolution currently defaults to 1024x768 as
161 Mac OS X Server falls back to the built-in EFI display support.
162 See <xref linkend="efividmode" /> for more information on how to
163 change EFI video modes.</para>
164 </listitem>
165
166 <listitem>
167 <para>Even when idle, Mac OS X Server guests currently burn 100%
168 CPU. This is a power management issue that will be addressed in a
169 future release.</para>
170 </listitem>
171
172 <listitem>
173 <para>Mac OS X Server guests only work with one CPU assigned to
174 the VM. Support for SMP will be provided in a future
175 release.</para>
176 </listitem>
177
178 <listitem>
179 <para>Depending on your system and version of Mac OS X Server, you
180 might experience guest hangs after some time. This can be fixed by
181 turning off energy saving (set timeout to "Never") in the system
182 preferences.</para>
183 </listitem>
184
185 <listitem>
186 <para>By default, the VirtualBox EFI enables debug output of the
187 Mac OS X Server kernel to help you diagnose boot problems. Note
188 that there is a lot of output and not all errors are fatal (they
189 would also show on your physical Mac). You can turn off these
190 messages by issuing this command:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" " "</screen>To
191 revert to the previous behavior, use:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" ""</screen></para>
192 </listitem>
193 </itemizedlist></para>
194 </listitem>
195
196 <listitem>
197 <para><emphasis role="bold">Solaris hosts:</emphasis> <itemizedlist>
198 <listitem>
199 <para>There is no support for USB devices connected to Solaris 10
200 hosts.</para>
201 </listitem>
202
203 <listitem>
204 <para>USB support on OpenSolaris hosts requires version snv_124 or
205 higher. Webcams and other isochronous devices are known to have
206 poor performance.</para>
207 </listitem>
208
209 <listitem>
210 <para>No ACPI information (battery status, power source) is
211 reported to the guest.</para>
212 </listitem>
213
214 <listitem>
215 <para>No support for using wireless adapters with bridged
216 networking.</para>
217 </listitem>
218 </itemizedlist></para>
219 </listitem>
220
221 <listitem>
222 <para><emphasis role="bold">Guest Additions for OS/2.</emphasis> Shared
223 folders are not yet supported with OS/2 guests. In addition, seamless
224 windows and automatic guest resizing will probably never be implemented
225 due to inherent limitations of the OS/2 graphics system.</para>
226 </listitem>
227 </itemizedlist>
228</chapter>
注意: 瀏覽 TracBrowser 來幫助您使用儲存庫瀏覽器

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