VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/settings-screen.dita

最後變更 在這個檔案是 108297,由 vboxsync 提交於 4 週 前

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

38ede4e3c915bbab9000b1b990e187daa07b4f61 Created 7.2 books from the 7.1 content with new part numbers, variables and removed non-7.2 content.
0951cfa5daf57ec2a81e36d335f14d8b4f2acd87 Merge branch 'Finalise_seamless_windows' into 'main'
b9e418eb08b28c6353e3f4534c7e360269cf5eef Included Klaus' feedback on known issues, moved some.
373130ebe466a21f4271e2ac36f11709c3697093 Initial edits to troubleshooting topics
a7459a9a24b73b4d268a751fba85e595ad6f35db Restructured and updated troubleshooting section
e3f67c800044e585a4428a4fc76016980269301b Added comments for future work
dcc46e566f3d269e5994d83cc5421532421fa639 Initial restructuring to move topics into suitable sections
e7b6f99bf86526813fcbe96903cf0c2652952eb0 removed Guest Control known issue. Info now in CLI topics
0209a6a155f460eaba79bcf0d0f34d8460413868 Reworded clipboard intro to be clear it requires GUI, made config a separate chapter
94f883f2b38dc281e759878880280370aa517d5c Included feedback from Brent on troubleshooting
ac1c0c919eeb58b1db478ca66e825ea89eb7a1a8 Removed preface, consolidated intro topics
7117e423ecdc1841b2bbca1aafda1c43ae38f7ea More restructuring and removing duplication
c8728eee82bd4081ab6f0500b32068c8f6749bc2 Updated intro and more restructuring
25389ab0df09df59f8f5f517f15590a917bb66a1 Added link to support and licensing
981ba048798bf7985f2c230fe97172d587e25fd6 7.2 updates for 3d acceleration
e95113d1da7ccf299642cd3368804e319e2bf3ca Updated diagram in intro, and filename
5c4555249e12738e55e9b8a0710f83ee7d4a9e61 New filenames, ids for intro
abf8d5092aea7f1fd4e9b7dbab578d615579eb4e Updated diagram to higher res

  • 屬性 svn:eol-style 設為 native
  • 屬性 svn:keywords 設為 Author Date Id Revision
檔案大小: 4.9 KB
 
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="settings-screen">
4 <title>Screen Tab</title>
5
6 <body>
7 <ul>
8 <li>
9 <p><b outputclass="bold">Video Memory:</b> Sets the size of the memory provided by the
10 virtual graphics card available to the guest, in megabytes. As with the main memory, the
11 specified amount will be allocated from the host's resident memory. Based on the amount of
12 video memory, higher resolutions and color depths may be available. </p>
13 <p><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> will show a warning if the amount of video memory is too small to be able to switch the VM into full screen mode. The minimum value depends on the number of virtual monitors, the screen resolution and the color depth of the host display as well as on the use of <i>3D acceleration</i>. A rough estimate is (<i>color depth</i> / 8) x <i>vertical pixels</i> x <i>horizontal pixels</i> x <i>number of screens</i> = <i>number of bytes</i>. Extra memory may be required if display acceleration is used. </p>
14 </li>
15 <li>
16 <p><b outputclass="bold">Monitor Count:</b> With this setting, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can provide more than one virtual monitor to a virtual machine. If a guest OS supports multiple attached monitors, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can pretend that multiple virtual monitors are present. Up to eight such virtual monitors are supported. </p>
17 <p>The output of the multiple monitors are displayed on the host in multiple VM windows which are running side by side. However, in full screen and seamless mode, they use the available physical monitors attached to the host. As a result, for full screen and seamless modes to work with multiple monitors, you will need at least as many physical monitors as you have virtual monitors configured, or <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will report an error. </p>
18 <p>You can configure the relationship between guest and host monitors using the <b outputclass="bold">View</b>
19 menu by pressing Host key + Home when you are in full screen or seamless mode. </p>
20 <p>See also <xref href="known-issues.dita"/>.</p>
21 </li>
22 <li>
23 <p><b outputclass="bold">Scale Factor:</b> Enables
24 scaling of the display size. For multiple monitor displays,
25 you can set the scale factor for individual monitors, or
26 globally for all of the monitors. Use the slider to select a
27 scaling factor up to 200%.
28 </p>
29 <p>You can set a default scale factor for all VMs. Use the <b outputclass="bold">Display</b> tab in the
30 Preferences window. </p>
31 </li>
32 <li>
33 <p><b outputclass="bold">Graphics Controller:</b>
34 Specifies the graphics adapter type used by the guest VM.
35 Note that you must install the Guest Additions on the guest
36 VM to specify the VBoxSVGA or VMSVGA graphics controller.
37 The following options are available:
38 </p>
39 <ul>
40 <li>
41 <p><b outputclass="bold">VBoxSVGA:</b> The default
42 graphics controller for new VMs that use Windows 7 or
43 later.
44 </p>
45 <p>This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option. </p>
46 </li>
47 <li>
48 <p><b outputclass="bold">VBoxVGA:</b> Use this
49 graphics controller for legacy guest OSes. This is the
50 default graphics controller for Windows versions before
51 Windows 7 and for Oracle Solaris.
52 </p>
53 <p>3D acceleration is not supported for this graphics controller. </p>
54 </li>
55 <li>
56 <p><b outputclass="bold">VMSVGA:</b> Use this
57 graphics controller to emulate a VMware SVGA graphics
58 device. This is the default graphics controller for
59 Linux guests.
60 </p>
61 </li>
62 <li>
63 <p><b outputclass="bold">None:</b> Does not emulate
64 a graphics adapter type.
65 </p>
66 </li>
67 </ul>
68 </li>
69 <li>
70 <p><b outputclass="bold">Enable 3D Acceleration:</b> If a virtual machine has Guest Additions installed, you can enable accelerated 3D graphics on the VM. See <xref href="guestadd-video.dita"/>.</p>
71 <p>With 3D acceleration enabled, the VM also uses video decoding acceleration if the host also supports video decoding acceleration. The host must be x86_64 running Windows or Linux, and the VM must be x86_64 running Windows 10 or Windows 11. The VM can use video decoding of all media formats that are supported by the host, and CPU load is reduced during playback of these media formats.</p>
72 </li>
73 </ul>
74 </body>
75
76</topic>
注意: 瀏覽 TracBrowser 來幫助您使用儲存庫瀏覽器

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