File: settings-screen.dita

package info (click to toggle)
virtualbox 7.1.12-dfsg-2
  • links: PTS, VCS
  • area: contrib
  • in suites: sid
  • size: 565,672 kB
  • sloc: ansic: 2,330,854; cpp: 2,193,228; asm: 230,777; python: 223,895; xml: 86,771; sh: 25,541; makefile: 8,158; perl: 5,697; java: 5,337; cs: 4,872; pascal: 1,782; javascript: 1,692; objc: 1,131; lex: 931; php: 906; sed: 899; yacc: 707
file content (86 lines) | stat: -rw-r--r-- 5,170 bytes parent folder | download
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
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic xml:lang="en-us" id="settings-screen">
  <title>Screen Tab</title>
  
  <body>
    <ul>
      <li>
        <p><b outputclass="bold">Video Memory:</b> Sets the size of the memory provided by the
          virtual graphics card available to the guest, in megabytes. As with the main memory, the
          specified amount will be allocated from the host's resident memory. Based on the amount of
          video memory, higher resolutions and color depths may be available. </p>
        <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>
      </li>
      <li>
        <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>
        <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>
        <p>You can configure the relationship between guest and host monitors using the <b outputclass="bold">View</b>
          menu by pressing Host key + Home when you are in full screen or seamless mode. </p>
        <p>See also <xref href="KnownIssues.dita">Known Limitations</xref>. </p>
      </li>
      <li>
        <p><b outputclass="bold">Scale Factor:</b> Enables
            scaling of the display size. For multiple monitor displays,
            you can set the scale factor for individual monitors, or
            globally for all of the monitors. Use the slider to select a
            scaling factor up to 200%.
          </p>
        <p>You can set a default scale factor for all VMs. Use the <b outputclass="bold">Display</b> tab in the
          Preferences window. </p>
      </li>
      <li>
        <p><b outputclass="bold">Graphics Controller:</b>
            Specifies the graphics adapter type used by the guest VM.
            Note that you must install the Guest Additions on the guest
            VM to specify the VBoxSVGA or VMSVGA graphics controller.
            The following options are available:
          </p>
        <ul>
          <li>
            <p><b outputclass="bold">VBoxSVGA:</b> The default
                graphics controller for new VMs that use Windows 7 or
                later.
              </p>
            <p>This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option. </p>
          </li>
          <li>
            <p><b outputclass="bold">VBoxVGA:</b> Use this
                graphics controller for legacy guest OSes. This is the
                default graphics controller for Windows versions before
                Windows 7 and for Oracle Solaris.
              </p>
            <p>3D acceleration is not supported for this graphics controller. </p>
          </li>
          <li>
            <p><b outputclass="bold">VMSVGA:</b> Use this
                graphics controller to emulate a VMware SVGA graphics
                device. This is the default graphics controller for
                Linux guests.
              </p>
          </li>
          <li>
            <p><b outputclass="bold">None:</b> Does not emulate
                a graphics adapter type.
              </p>
          </li>
        </ul>
      </li>
      <li>
        <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>
        <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, 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>
      </li>
    </ul>
  </body>
  
</topic>