1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"[
<!ENTITY % all.entities SYSTEM "all-entities.ent">
%all.entities;
]>
<chapter id="KnownIssues">
<title>Known Limitations</title>
<sect1 id="ExperimentalFeatures">
<title>Experimental Features</title>
<para>
Some &product-name; features are labeled as experimental. Such
features are provided on an "as-is" basis and are not formally
supported. However, feedback and suggestions about such features
are welcome. A comprehensive list of experimental features is as
follows:
</para>
<itemizedlist>
<listitem>
<para>
Hardware 3D acceleration support for Windows, Linux, and
Oracle Solaris guests
</para>
</listitem>
<listitem>
<para>
Hardware 2D video playback acceleration support for Windows
guests
</para>
</listitem>
<!-- <listitem>
<para>
PCI passthrough (Linux hosts only)
</para>
</listitem>-->
<listitem>
<para>
Mac OS X guests (Mac OS X hosts only)
</para>
</listitem>
<listitem>
<para>
ICH9 chipset emulation
</para>
</listitem>
<listitem>
<para>
EFI firmware
</para>
</listitem>
<listitem>
<para>
Host CD/DVD drive passthrough
</para>
</listitem>
<listitem>
<para>
Support of iSCSI using internal networking
</para>
</listitem>
<listitem>
<para>
Using &product-name; and Hyper-V on the same host
</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="KnownProblems">
<title>Known Issues</title>
<para>
The following section describes known problems with this release
of &product-name;. Unless marked otherwise, these issues are
planned to be fixed in later releases.
</para>
<itemizedlist>
<listitem>
<para>
Poor performance when using &product-name; and
<emphasis role="bold">Hyper-V</emphasis> on the same host. To
fix this, certain Windows features like "Hyper-V Platform",
"Virtual Machine Platform" and "Windows Hypervisor Platform"
must be turned off, followed by a host reboot.
</para>
<para>
Additionally, the Microsoft Device Guard and Credential Guard
hardware readiness tool might have to be used in order to turn
off more features. For example, by running the following
command:
</para>
<screen>.\DG_Readiness_Tool_vX.X.ps1 -Disable -AutoReboot</screen>
<note>
<para>
Disabling Device Guard and Credential Guard features will
have an impact on the overall security of the host. Please
contact your Administrator beforehand regarding this.
</para>
</note>
</listitem>
<listitem>
<para>
The following <emphasis role="bold">Guest SMP (multiprocessor)
limitations</emphasis> exist:
</para>
<itemizedlist>
<listitem>
<para>
<emphasis role="bold">Poor performance</emphasis> with
32-bit guests on AMD CPUs. This affects mainly Windows and
Oracle Solaris guests, but possibly also some Linux kernel
revisions. Partially solved for 32-bit Windows NT, 2000,
XP, and 2003 guests. Requires the Guest Additions to be
installed.
</para>
</listitem>
<listitem>
<para>
<emphasis role="bold">Poor performance</emphasis> with
32-bit guests on certain Intel CPU models that do not
include virtual APIC hardware optimization support. This
affects mainly Windows and Oracle Solaris guests, but
possibly also some Linux kernel revisions. Partially
solved for 32-bit Windows NT, 2000, XP, and 2003 guests.
Requires the Guest Additions to be installed.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
<emphasis role="bold">NX (no execute, data execution
prevention)</emphasis> only works for guests running on 64-bit
hosts and requires that hardware virtualization be enabled.
</para>
</listitem>
<listitem>
<para>
<emphasis role="bold">Guest control.</emphasis> On Windows
guests, a process started using the guest control execute
support will not be able to display a graphical user interface
<emphasis>unless</emphasis> the user account under which it is
running is currently logged in and has a desktop session.
</para>
<para>
Also, to use accounts without or with an empty password, the
guest's group policy must be changed. To do so, open the group
policy editor on the command line by typing
<command>gpedit.msc</command>, open the key <literal>Computer
Configuration\Windows Settings\Security Settings\Local
Policies\Security Options</literal> and change the value of
<literal>Accounts: Limit local account use of blank passwords
to console logon only</literal> to Disabled.
</para>
</listitem>
<listitem>
<para>
<emphasis role="bold">Compacting virtual disk images is
limited to VDI files.</emphasis> The <command>VBoxManage
modifymedium --compact</command> command is currently only
implemented for VDI files. At the moment the only way to
optimize the size of a virtual disk images in other formats,
such as VMDK or VHD, is to clone the image and then use the
cloned image in the VM configuration.
</para>
</listitem>
<listitem>
<para>
<emphasis role="bold">OVF import/export:</emphasis>
</para>
<itemizedlist>
<listitem>
<para>
OVF localization, with multiple languages in a single OVF
file, is not yet supported.
</para>
</listitem>
<listitem>
<para>
Some OVF sections like StartupSection,
DeploymentOptionSection, and InstallSection are ignored.
</para>
</listitem>
<listitem>
<para>
OVF environment documents, including their property
sections and appliance configuration with ISO images, are
not yet supported.
</para>
</listitem>
<listitem>
<para>
Remote files using HTTP or other mechanisms are not yet
supported.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
Neither <emphasis role="bold">scale mode</emphasis> nor
<emphasis role="bold">seamless mode</emphasis> work correctly
with guests using OpenGL 3D features, such as with
Compiz-enabled window managers.
</para>
</listitem>
<listitem>
<para>
The RDP server in the &product-name; extension pack supports
only audio streams in format 22.05kHz stereo 16-bit. If the
RDP client requests any other audio format there will be no
audio.
</para>
</listitem>
<listitem>
<para>
Preserving the aspect ratio in scale mode works only on
Windows hosts and on Mac OS X hosts.
</para>
</listitem>
<listitem>
<para>
On <emphasis role="bold">Mac OS X hosts,</emphasis> the
following features are not yet implemented:
</para>
<itemizedlist>
<listitem>
<para>
Numlock emulation
</para>
</listitem>
<listitem>
<para>
CPU frequency metric
</para>
</listitem>
<listitem>
<para>
Memory ballooning
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
<emphasis role="bold">Mac OS X guests:</emphasis>
</para>
<itemizedlist>
<listitem>
<para>
Mac OS X guests can only run on a certain host hardware.
For details about license and host hardware limitations.
See <xref linkend="intro-macosxguests" /> and check the
Apple software license conditions.
</para>
</listitem>
<listitem>
<para>
&product-name; does not provide Guest Additions for Mac OS
X at this time.
</para>
</listitem>
<listitem>
<para>
The graphics resolution currently defaults to 1024x768 as
Mac OS X falls back to the built-in EFI display support.
See <xref linkend="efividmode" /> for more information on
how to change EFI video modes.
</para>
</listitem>
<listitem>
<para>
Mac OS X guests only work with one CPU assigned to the VM.
Support for SMP will be provided in a future release.
</para>
</listitem>
<listitem>
<para>
Depending on your system and version of Mac OS X, you
might experience guest hangs after some time. This can be
fixed by turning off energy saving. Set the timeout to
"Never" in the system preferences.
</para>
</listitem>
<listitem>
<para>
By default, the &product-name; EFI enables debug output of
the Mac OS X kernel to help you diagnose boot problems.
Note that there is a lot of output and not all errors are
fatal. They would also show when using a physical Apple
Macintosh computer. You can turn off these messages by
using the following command:
</para>
<screen>$ VBoxManage setextradata <replaceable>VM-name</replaceable> "VBoxInternal2/EfiBootArgs" " "</screen>
<para>
To revert to the previous behavior, use the following
command:
</para>
<screen>$ VBoxManage setextradata <replaceable>VM-name</replaceable> "VBoxInternal2/EfiBootArgs" ""</screen>
</listitem>
<listitem>
<para>
It is currently not possible to start a Mac OS X guest in
safe mode by specifying the <option>-x</option> option in
<literal>VBoxInternal2/EfiBootArgs</literal> extradata.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
<emphasis role="bold">Oracle Solaris hosts:</emphasis>
</para>
<itemizedlist>
<listitem>
<para>
USB support on Oracle Solaris hosts requires Oracle
Solaris 11 version snv_124 or later. Webcams and other
isochronous devices are known to have poor performance.
</para>
</listitem>
<listitem>
<para>
Host Webcam passthrough is restricted to 640x480 frames at
20 frames per second due to limitations in the Oracle
Solaris V4L2 API. This may be addressed in a future Oracle
Solaris release.
</para>
</listitem>
<listitem>
<para>
No ACPI information, such as battery status or power
source, is reported to the guest.
</para>
</listitem>
<listitem>
<para>
No support for using wireless adapters with bridged
networking.
</para>
</listitem>
<listitem>
<para>
Crossbow-based bridged networking on Oracle Solaris 11
hosts does not work directly with aggregate links.
However, you can use <command>dladm</command> to manually
create a VNIC over the aggregate link and use that with a
VM. This limitation does not exist in Oracle Solaris 11u1
build 17 and later.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
Neither virtio nor Intel PRO/1000 drivers for
<emphasis role="bold">Windows XP guests</emphasis> support
segmentation offloading. Therefore Windows XP guests have
slower transmission rates comparing to other guest types.
Refer to MS Knowledge base article 842264 for additional
information.
</para>
</listitem>
<listitem>
<para>
<emphasis role="bold">Guest Additions for OS/2.</emphasis>
Seamless windows and automatic guest resizing will probably
never be implemented due to inherent limitations of the OS/2
graphics system.
</para>
</listitem>
<listitem>
<para>
Some guest operating systems predating ATAPI CD-ROMs may
exhibit long delays or entirely fail to boot in certain
configurations. This is most likely to happen when an
IDE/ATAPI CD-ROM exists alone on a primary or secondary IDE
channel.
</para>
<para>
Affected operating systems are MS OS/2 1.21: fails to boot
with an error message referencing COUNTRY.SYS and MS OS/2 1.3:
long boot delays. To avoid such problems, disable the emulated
IDE/ATAPI CD-ROM. The guest OS cannot use this device, anyway.
</para>
</listitem>
</itemizedlist>
</sect1>
</chapter>
|