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>
|
---|
14 | <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> will show a warning if the amount of video memory
|
---|
15 | is too small to be able to switch the VM into full screen
|
---|
16 | mode. The minimum value depends on the number of virtual
|
---|
17 | monitors, the screen resolution and the color depth of the
|
---|
18 | host display as well as on the use of <i>3D
|
---|
19 | acceleration</i> and <i>2D video
|
---|
20 | acceleration</i>. A rough estimate is
|
---|
21 | (<i>color depth</i> / 8) x <i>vertical
|
---|
22 | pixels</i> x <i>horizontal pixels</i> x
|
---|
23 | <i>number of screens</i> = <i>number of
|
---|
24 | bytes</i>. Extra memory may be required if display
|
---|
25 | acceleration is used.
|
---|
26 | </p>
|
---|
27 | </li>
|
---|
28 | <li>
|
---|
29 | <p><b outputclass="bold">Monitor Count:</b> With this
|
---|
30 | setting, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can provide more than one virtual
|
---|
31 | monitor to a virtual machine. If a guest OS supports
|
---|
32 | multiple attached monitors, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can pretend that
|
---|
33 | multiple virtual monitors are present. Up to eight such
|
---|
34 | virtual monitors are supported.
|
---|
35 | </p>
|
---|
36 | <p>
|
---|
37 | The output of the multiple monitors are displayed on the
|
---|
38 | host in multiple VM windows which are running side by side.
|
---|
39 | However, in full screen and seamless mode, they use the
|
---|
40 | available physical monitors attached to the host. As a
|
---|
41 | result, for full screen and seamless modes to work with
|
---|
42 | multiple monitors, you will need at least as many physical
|
---|
43 | monitors as you have virtual monitors configured, or
|
---|
44 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will report an error.
|
---|
45 | </p>
|
---|
46 | <p>
|
---|
47 | You can configure the relationship between guest and host
|
---|
48 | monitors using the <b outputclass="bold">View</b>
|
---|
49 | menu by pressing Host key + Home when you are in full screen
|
---|
50 | or seamless mode.
|
---|
51 | </p>
|
---|
52 | <p>
|
---|
53 | See also <xref href="KnownIssues.dita">Known Limitations</xref>.
|
---|
54 | </p>
|
---|
55 | </li>
|
---|
56 | <li>
|
---|
57 | <p><b outputclass="bold">Scale Factor:</b> Enables
|
---|
58 | scaling of the display size. For multiple monitor displays,
|
---|
59 | you can set the scale factor for individual monitors, or
|
---|
60 | globally for all of the monitors. Use the slider to select a
|
---|
61 | scaling factor up to 200%.
|
---|
62 | </p>
|
---|
63 | <p>
|
---|
64 | You can set a default scale factor for all VMs. Use the
|
---|
65 | <b outputclass="bold">Display</b> tab in the
|
---|
66 | Preferences window.
|
---|
67 | </p>
|
---|
68 | </li>
|
---|
69 | <li>
|
---|
70 | <p><b outputclass="bold">Graphics Controller:</b>
|
---|
71 | Specifies the graphics adapter type used by the guest VM.
|
---|
72 | Note that you must install the Guest Additions on the guest
|
---|
73 | VM to specify the VBoxSVGA or VMSVGA graphics controller.
|
---|
74 | The following options are available:
|
---|
75 | </p>
|
---|
76 | <ul>
|
---|
77 | <li>
|
---|
78 | <p><b outputclass="bold">VBoxSVGA:</b> The default
|
---|
79 | graphics controller for new VMs that use Windows 7 or
|
---|
80 | later.
|
---|
81 | </p>
|
---|
82 | <p>
|
---|
83 | This graphics controller improves performance and 3D
|
---|
84 | support when compared to the legacy VBoxVGA option.
|
---|
85 | </p>
|
---|
86 | </li>
|
---|
87 | <li>
|
---|
88 | <p><b outputclass="bold">VBoxVGA:</b> Use this
|
---|
89 | graphics controller for legacy guest OSes. This is the
|
---|
90 | default graphics controller for Windows versions before
|
---|
91 | Windows 7 and for Oracle Solaris.
|
---|
92 | </p>
|
---|
93 | <p>
|
---|
94 | 3D acceleration is not supported for this graphics
|
---|
95 | controller.
|
---|
96 | </p>
|
---|
97 | </li>
|
---|
98 | <li>
|
---|
99 | <p><b outputclass="bold">VMSVGA:</b> Use this
|
---|
100 | graphics controller to emulate a VMware SVGA graphics
|
---|
101 | device. This is the default graphics controller for
|
---|
102 | Linux guests.
|
---|
103 | </p>
|
---|
104 | </li>
|
---|
105 | <li>
|
---|
106 | <p><b outputclass="bold">None:</b> Does not emulate
|
---|
107 | a graphics adapter type.
|
---|
108 | </p>
|
---|
109 | </li>
|
---|
110 | </ul>
|
---|
111 | </li>
|
---|
112 | <li>
|
---|
113 | <p><b outputclass="bold">Enable 3D Acceleration:</b> If
|
---|
114 | a virtual machine has Guest Additions installed, you can
|
---|
115 | select here whether the guest should support accelerated 3D
|
---|
116 | graphics. See <xref href="guestadd-3d.dita#guestadd-3d"/>.
|
---|
117 | </p>
|
---|
118 | </li>
|
---|
119 | </ul>
|
---|
120 | </body>
|
---|
121 |
|
---|
122 | </topic>
|
---|