diff options
Diffstat (limited to 'doc/manual/en_US/user_KnownIssues.xml')
| -rw-r--r-- | doc/manual/en_US/user_KnownIssues.xml | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/doc/manual/en_US/user_KnownIssues.xml b/doc/manual/en_US/user_KnownIssues.xml index da7a4d01..9953de76 100644 --- a/doc/manual/en_US/user_KnownIssues.xml +++ b/doc/manual/en_US/user_KnownIssues.xml @@ -80,6 +80,13 @@ experience this, do not attempt to execute 64-bit guests. Refer to the VirtualBox user forum for additional information.</para> </listitem> + + <listitem> + <para><emphasis role="bold">NX (no execute, data execution + prevention)</emphasis> only works for guests running on 64-bit hosts + or guests running on 32-bit hosts with PAE enabled and requires that + hardware virtualization be enabled.</para> + </listitem> <listitem> <para>For <emphasis role="bold">basic Direct3D support in Windows @@ -206,12 +213,6 @@ </listitem> <listitem> - <para>Even when idle, Mac OS X guests currently burn 100% CPU. - This is a power management issue that will be addressed in a - future release.</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> @@ -278,7 +279,7 @@ </note> To solve this problem, one should uninstall the VirtualBox WDDM Video driver manually. To do that open Device Manager, and check whether the Display Adapter is named - "VirtualBox Graphics Adapter ..". If no - there is nothing to be done. If yes - right-clik + "VirtualBox Graphics Adapter ..". If no - there is nothing to be done. If yes - right-click the VirtualBox Graphics Adapter in Device Manager, select "Uninstall", check "Delete the driver software for this device" and click "OK". Once uninstallation is done - in Device Manager go to menu "Action" and select "Scan for hardware changes" to make the propper (Windows default) driver be picked up for the Graphics adapter. |