VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/KnownProblems.dita@ 105938

Last change on this file since 105938 was 105938, checked in by vboxsync, 5 months ago

Docs: bugref:10705. The following commits from doc's team git repo has been applied:

a01f320e6b877faebb42bdc332d5e5c8d610c4d9 Review feedback from dev team.
855b8fa5a09bb681f6d0f2bf2ec16728c4371380 Fixed topic IDs, added network hardware info, and updated guest additions for Arm info.
3c9efcf403508ac38b8474a3098469905ecd4a09 VBP_941 Removed graphics and comments
e19f6026b920878833da0b85915ee4bc0bf6b132 Created a new folder for all cli topics (manpages) that are sourced from the...

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