KnownProblems.dita@ 105293

Last change on this file since 105293 was 105176, checked in by vboxsync, 7 months ago
Docs: bugref:10705. Merging some more changes from docs team's dita topic files. not complete.
Property svn:eol-style set to `native` Property svn:keywords set to `Author Date Id Revision`
File size: 12.2 KB

Line
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="KnownProblems">
4	<title>Known Issues</title>
5
6	<body>
7	<p>
8	The following section describes known problems with this release
9	of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. Unless marked otherwise, these issues are
10	planned to be fixed in later releases.
11	</p>
12	<ul>
13	<li>
14	<p>
15	The macOS installer packages for <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7 currently do
16	not include the Internal Networking feature, which is
17	available on all other platforms. This will be addressed with
18	an update of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7. For setups which depend on this
19	functionality it is best to keep using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 6.1.
20	</p>
21	</li>
22	<li>
23	<p>
24	Poor performance when using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and
25	<b outputclass="bold">Hyper-V</b> on the same host. To
26	fix this, certain Windows features like "Hyper-V Platform",
27	"Virtual Machine Platform" and "Windows Hypervisor Platform"
28	must be turned off, followed by a host reboot.
29	</p>
30	<p>
31	Additionally, the Microsoft Device Guard and Credential Guard
32	hardware readiness tool might have to be used in order to turn
33	off more features. For example, by running the following
34	command:
35	</p>
36	<pre xml:space="preserve">.\DG_Readiness_Tool_vX.X.ps1 -Disable -AutoReboot</pre>
37	<note>
38	<p>
39	Disabling Device Guard and Credential Guard features will
40	have an impact on the overall security of the host. Please
41	contact your Administrator beforehand regarding this.
42	</p>
43	</note>
44	</li>
45	<li>
46	<p>
47	The following <b outputclass="bold">Guest SMP (multiprocessor)
48	limitations</b> exist:
49	</p>
50	<ul>
51	<li>
52	<p><b outputclass="bold">Poor performance</b> with
53	32-bit guests on AMD CPUs. This affects mainly Windows and
54	Oracle Solaris guests, but possibly also some Linux kernel
55	revisions. Partially solved for 32-bit Windows NT, 2000,
56	XP, and 2003 guests. Requires the Guest Additions to be
57	installed.
58	</p>
59	</li>
60	<li>
61	<p><b outputclass="bold">Poor performance</b> with
62	32-bit guests on certain Intel CPU models that do not
63	include virtual APIC hardware optimization support. This
64	affects mainly Windows and Oracle Solaris guests, but
65	possibly also some Linux kernel revisions. Partially
66	solved for 32-bit Windows NT, 2000, XP, and 2003 guests.
67	Requires the Guest Additions to be installed.
68	</p>
69	</li>
70	</ul>
71	</li>
72	<li>
73	<p><b outputclass="bold">NX (no execute, data execution
74	prevention)</b> only works for guests running on 64-bit
75	hosts and requires that hardware virtualization be enabled.
76	</p>
77	</li>
78	<li>
79	<p><b outputclass="bold">Guest control.</b> On Windows
80	guests, a process started using the guest control execute
81	support will not be able to display a graphical user interface
82	<i>unless</i> the user account under which it is
83	running is currently logged in and has a desktop session.
84	</p>
85	<p>
86	Also, to use accounts without or with an empty password, the
87	guest's group policy must be changed. To do so, open the group
88	policy editor on the command line by typing
89	<userinput>gpedit.msc</userinput>, open the key <codeph>Computer
90	Configuration\Windows Settings\Security Settings\Local
91	Policies\Security Options</codeph> and change the value of
92	<codeph>Accounts: Limit local account use of blank passwords
93	to console logon only</codeph> to Disabled.
94	</p>
95	</li>
96	<li>
97	<p><b outputclass="bold">Compacting virtual disk images is
98	limited to VDI files.</b> The <userinput>VBoxManage
99	modifymedium --compact</userinput> command is currently only
100	implemented for VDI files. At the moment the only way to
101	optimize the size of a virtual disk images in other formats,
102	such as VMDK or VHD, is to clone the image and then use the
103	cloned image in the VM configuration.
104	</p>
105	</li>
106	<li>
107	<p>
108	<b outputclass="bold">OVF import/export:</b>
109	</p>
110	<ul>
111	<li>
112	<p>
113	OVF localization, with multiple languages in a single OVF
114	file, is not yet supported.
115	</p>
116	</li>
117	<li>
118	<p>
119	Some OVF sections like StartupSection,
120	DeploymentOptionSection, and InstallSection are ignored.
121	</p>
122	</li>
123	<li>
124	<p>
125	OVF environment documents, including their property
126	sections and appliance configuration with ISO images, are
127	not yet supported.
128	</p>
129	</li>
130	<li>
131	<p>
132	Remote files using HTTP or other mechanisms are not yet
133	supported.
134	</p>
135	</li>
136	</ul>
137	</li>
138	<li>
139	<p>
140	Neither <b outputclass="bold">scale mode</b> nor
141	<b outputclass="bold">seamless mode</b> work correctly
142	with guests using OpenGL 3D features, such as with
143	Compiz-enabled window managers.
144	</p>
145	</li>
146	<li>
147	<p>
148	The RDP server in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension pack supports
149	only audio streams in format 22.05kHz stereo 16-bit. If the
150	RDP client requests any other audio format there will be no
151	audio.
152	</p>
153	</li>
154	<li>
155	<p>
156	Preserving the aspect ratio in scale mode works only on
157	Windows hosts and on macOS hosts.
158	</p>
159	</li>
160	<li>
161	<p>
162	On <b outputclass="bold">macOS hosts</b>, the following
163	features are not yet implemented:
164	</p>
165	<ul>
166	<li>
167	<p>
168	Numlock emulation
169	</p>
170	</li>
171	<li>
172	<p>
173	CPU frequency metric
174	</p>
175	</li>
176	<li>
177	<p>
178	Memory ballooning
179	</p>
180	</li>
181	</ul>
182	</li>
183	<li>
184	<p>
185	<b outputclass="bold">macOS/Arm64 (Apple silicon) host
186	package</b>
187	</p>
188	</li>
189	<li>
190	<p>
191	<b outputclass="bold">Mac OS X guests:</b>
192	</p>
193	<ul>
194	<li>
195	<p>
196	Mac OS X guests can only run on a certain host hardware.
197	For details about license and host hardware limitations.
198	See <xref href="intro-macosxguests.dita">Mac OS X Guests</xref> and check the
199	Apple software license conditions.
200	</p>
201	</li>
202	<li>
203	<p>
204	<ph conkeyref="vbox-conkeyref-phrases/product-name"/> does not provide Guest Additions for Mac OS
205	X at this time.
206	</p>
207	</li>
208	<li>
209	<p>
210	The graphics resolution currently defaults to 1024x768 as
211	Mac OS X falls back to the built-in EFI display support.
212	See <xref href="efividmode.dita">Video Modes in EFI</xref> for more information on
213	how to change EFI video modes.
214	</p>
215	</li>
216	<li>
217	<p>
218	Mac OS X guests only work with one CPU assigned to the VM.
219	Support for SMP will be provided in a future release.
220	</p>
221	</li>
222	<li>
223	<p>
224	Depending on your system and version of Mac OS X, you
225	might experience guest hangs after some time. This can be
226	fixed by turning off energy saving. Set the timeout to
227	"Never" in the system preferences.
228	</p>
229	</li>
230	<li>
231	<p>
232	By default, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> EFI enables debug output of
233	the Mac OS X kernel to help you diagnose boot problems.
234	Note that there is a lot of output and not all errors are
235	fatal. They would also show when using a physical Apple
236	Macintosh computer. You can turn off these messages by
237	using the following command:
238	</p>
239	<pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> "VBoxInternal2/EfiBootArgs" " "</pre>
240	<p>
241	To revert to the previous behavior, use the following
242	command:
243	</p>
244	<pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> "VBoxInternal2/EfiBootArgs" ""</pre>
245	</li>
246	<li>
247	<p>
248	It is currently not possible to start a Mac OS X guest in
249	safe mode by specifying the <codeph>-x</codeph> option in
250	<codeph>VBoxInternal2/EfiBootArgs</codeph> extradata.
251	</p>
252	</li>
253	</ul>
254	</li>
255	<li>
256	<p>
257	<b outputclass="bold">Oracle Solaris hosts:</b>
258	</p>
259	<ul>
260	<li>
261	<p>
262	USB support on Oracle Solaris hosts requires Oracle
263	Solaris 11 version snv_124 or later. Webcams and other
264	isochronous devices are known to have poor performance.
265	</p>
266	</li>
267	<li>
268	<p>
269	Host Webcam passthrough is restricted to 640x480 frames at
270	20 frames per second due to limitations in the Oracle
271	Solaris V4L2 API. This may be addressed in a future Oracle
272	Solaris release.
273	</p>
274	</li>
275	<li>
276	<p>
277	No ACPI information, such as battery status or power
278	source, is reported to the guest.
279	</p>
280	</li>
281	<li>
282	<p>
283	No support for using wireless adapters with bridged
284	networking.
285	</p>
286	</li>
287	<li>
288	<p>
289	Crossbow-based bridged networking on Oracle Solaris 11
290	hosts does not work directly with aggregate links.
291	However, you can use <userinput>dladm</userinput> to manually
292	create a VNIC over the aggregate link and use that with a
293	VM. This limitation does not exist in Oracle Solaris 11u1
294	build 17 and later.
295	</p>
296	</li>
297	</ul>
298	</li>
299	<li>
300	<p>
301	Neither virtio nor Intel PRO/1000 drivers for
302	<b outputclass="bold">Windows XP guests</b> support
303	segmentation offloading. Therefore Windows XP guests have
304	slower transmission rates comparing to other guest types.
305	Refer to MS Knowledge base article 842264 for additional
306	information.
307	</p>
308	</li>
309	<li>
310	<p><b outputclass="bold">Guest Additions for OS/2.</b>
311	Seamless windows and automatic guest resizing will probably
312	never be implemented due to inherent limitations of the OS/2
313	graphics system.
314	</p>
315	</li>
316	<li>
317	<p>
318	Some guest operating systems predating ATAPI CD-ROMs may
319	exhibit long delays or entirely fail to boot in certain
320	configurations. This is most likely to happen when an
321	IDE/ATAPI CD-ROM exists alone on a primary or secondary IDE
322	channel.
323	</p>
324	<p>
325	Affected operating systems are MS OS/2 1.21: fails to boot
326	with an error message referencing COUNTRY.SYS and MS OS/2 1.3:
327	long boot delays. To avoid such problems, disable the emulated
328	IDE/ATAPI CD-ROM. The guest OS cannot use this device, anyway.
329	</p>
330	</li>
331	</ul>
332	</body>
333
334	</topic>

Note: See TracBrowser for help on using the repository browser.

Download in other formats:

Original Format