VirtualBox

Changeset 108796 in vbox


Ignore:
Timestamp:
Mar 31, 2025 12:45:50 PM (6 weeks ago)
Author:
vboxsync
svn:sync-xref-src-repo-rev:
168239
Message:

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

2c0019d3093908ca1ee634d7b1811c0013b6ebbc Tidied up guest additions section
954c4a0bff90b9688bd723df2b6273e59f88577c Updated installation of guest additions and removed duplication between topics
a4792940a9457bfbaaf0c95aabd601ea3d78bd62 Further updates to guest additions installation and update
1d7f4f4e4f178322f0809b3342137b75587b2502 Dev feedback on GA changes
b2e482309d405433a778468d4a531e72abb5f3da Moved rcvboxadd instruction
493a7500aae18ae2414d0437782860cc2fbce03f Changed x86-64 to x86_64 for consistency. Added topic ID prefixes as test.
7202928f3c99e9de07b2d06779f53a0650fdd174 Moved files from advanced topics
545bf4121f5e8de9907bd2ef08378a233256881e Vbp 1285 video enc

Location:
trunk/doc/manual/en_US/dita
Files:
2 added
6 deleted
26 edited

Legend:

Unmodified
Added
Removed

  • trunk/doc/manual/en_US/dita/UserManual.ditamap

    r108750 r108796  
    211211               <topicref href="topics/mountingadditionsiso.dita"/>
    212212               <topicref href="topics/additions-windows-updating.dita"/>
    213                <topicref href="topics/additions-windows-install-unattended.dita"/>
    214213               <topicref href="topics/additions-windows-install-unattended-certs.dita"/>
     214        <topicref href="topics/sysprep.dita"/>
    215215               <topicref href="topics/windows-guest-file-extraction.dita"/>
    216216            </topicref>
    217217            <topicref href="topics/additions-linux.dita">
    218218               <topicref href="topics/additions-linux-install.dita"/>
    219                <topicref href="topics/additions-linux-install-unattended.dita"/>
    220                <topicref href="topics/additions-linux-graphics-mouse.dita"/>
     219        <topicref href="topics/linux-guest-manual-setup.dita"/>
    221220               <topicref href="topics/additions-linux-updating.dita"/>
    222221               <topicref href="topics/additions-linux-uninstall.dita"/>
    … …  
    224223            <topicref href="topics/additions-solaris.dita">
    225224               <topicref href="topics/additions-solaris-install.dita"/>
    226                <topicref href="topics/additions-solaris-install-unattended.dita"/>
    227225               <topicref href="topics/additions-solaris-uninstall.dita"/>
    228226               <topicref href="topics/additions-solaris-updating.dita"/>
    … …  
    230228            <topicref href="topics/additions-os2.dita"/>
    231229         </topicref>
     230    <topicref href="topics/additions-linux-graphics-mouse.dita">
     231      <topicref href="topics/vboxdrmclient.dita"/>
     232    </topicref>
    232233         <topicref href="topics/sharedfolders.dita">
    233234            <topicref href="topics/sf_mount_manual.dita"/>
    … …  
    334335         </topicref>
    335336      </topicref>
    336       <topicref href="topics/adv-config-win-guest.dita">
    337          <topicref href="topics/sysprep.dita"/>
    338       </topicref>
    339       <topicref href="topics/adv-config-linux-guest.dita">
    340          <topicref href="topics/linux-guest-manual-setup.dita"/>
    341          <topicref href="topics/guestxorgsetup.dita"/>
    342       </topicref>
    343337      <topicref href="topics/cpuhotplug.dita"/>
    344338      <topicref href="topics/webcam-passthrough.dita">
    … …  
    474468      <topicref href="topics/ts_config-periodic-flush.dita"/>
    475469      <topicref href="topics/ts_linux-buggy.dita"/>
     470      <topicref href="topics/ts_crash_startup_kernel_issue.dita"/>
    476471      <topicref href="topics/ts_linux-guest-high-cpu.dita"/>
    477472      <topicref href="topics/ts_solaris-10-guest-slow-boot-smp.dita"/>

  • trunk/doc/manual/en_US/dita/topics/additions-linux-graphics-mouse.dita

    r105388 r108796  
    55 
    66  <body>
    7     <p>In Linux and Oracle Solaris guests, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphics and mouse
    8       integration goes through the X Window System. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can use the
    9       X.Org variant of the system, or XFree86 version 4.3 which is identical to the first X.Org release. During the
    10       installation process, the X.Org display server will be set up to use the graphics and mouse drivers which come
    11       with the Guest Additions. </p>
    12     <p>After installing the Guest Additions into a fresh installation of a supported Linux distribution or Oracle
    13       Solaris system, many unsupported systems will work correctly too, the guest's graphics mode will change to fit the
    14       size of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> window on the host when it is resized. You can
    15       also ask the guest system to switch to a particular resolution by sending a video mode hint using the
    16         <userinput>VBoxManage</userinput> tool. </p>
    17     <p>Multiple guest monitors are supported in guests using the X.Org server version 1.3, which is part of release 7.3
    18       of the X Window System version 11, or a later version. The layout of the guest screens can be adjusted as needed
    19       using the tools which come with the guest operating system. </p>
    20     <p>If you want to understand more about the details of how the X.Org drivers are set up, in particular if you want
    21       to use them in a setting which our installer does not handle correctly, see <xref href="guestxorgsetup.dita">Guest
    22         Graphics and Mouse Driver Setup in Depth</xref>. </p>
    23     <p>Starting from <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7, Linux guest screen resize functionality
    24       for guests running VMSVGA graphics configuration has been changed. Since then, this functionality consists of a
    25       standalone daemon called VBoxDRMClient and its Desktop Environment helper counterpart. </p>
    26     <p>VBoxDRMClient runs as a root process and is a bridge between the host and the guest's vmwgfx driver. This means
    27       that VBoxDRMClient listens to screen resize hints from the host and forwards them to the vmwgfx driver. This
    28       enables guest screen resize functionality to be available before the user has performed a graphical login. </p>
    29     <p>In order to perform Desktop Environment specific actions, such as setting the primary screen in a multimonitor
    30       setup, a Desktop Environment helper is used. Once the user has performed a graphical login operation, the helper
    31       daemon starts with user session scope and attempts to connect to VBoxDRMClient using an IPC connection. When
    32       VBoxDRMClient has received a corresponding command from the host, it is forwarded to the helper daemon over IPC
    33       and the action is then performed. </p>
    34     <p>By default, VBoxDRMClient allows any process to connect to its IPC socket. This can be restricted by using the
    35       following steps: </p>
    36     <ol>
    37       <li>
    38         <p>The Guest Additions Linux installer creates a <codeph>vboxdrmipc</codeph> user group. A corresponding user
    39           needs to be added to this group. </p>
    40       </li>
    41       <li>
    42         <p>You must set the <codeph>DRMIpcRestricted</codeph> guest property, as follows: </p>
    43         <pre xml:space="preserve">VBoxManage guestproperty set "VM name" /VirtualBox/GuestAdd/DRMIpcRestricted 1 \
    44 --flags RDONLYGUEST</pre>
    45         <p>It is important to set only the RDONLYGUEST flag for the property, so that it cannot be changed from inside
    46           the guest. </p>
    47       </li>
    48     </ol>
    49     <note>
    50       <p>Both steps are required. If one of them is missing, all processes will have access to the IPC socket. </p>
    51     </note>
    52     <p>Restricted mode can be disabled by unsetting the guest property, as follows: </p>
    53     <pre xml:space="preserve">VBoxManage guestproperty unset "VM name" /VirtualBox/GuestAdd/DRMIpcRestricted</pre>
     7    <p>In Linux and Oracle Solaris guests, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphics and mouse integration goes through the <?oxy_comment_start author="Mhari Duncan" timestamp="20250326T172823+0000" comment="Add Wayland"?>X Window System<?oxy_comment_end?>. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can use the X.Org variant of the system, or XFree86 version 4.3 which is identical to the first X.Org release. During the installation process, the X.Org display server will be set up to use the graphics and mouse drivers that come with the Guest Additions.</p>
     8    <p>After installing the Guest Additions into a fresh installation of most Linux distributions or Oracle Solaris systems, the guest's graphics mode will change to fit the size of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> window on the host when it is resized. You can also ask the guest system to switch to a particular resolution by sending a video mode hint using the <userinput>VBoxManage</userinput> tool.</p>
     9    <p>Multiple guest monitors are supported in guests using the X.Org server version 1.3, which is part of release 7.3 of the X Window System version 11, or a later version. The layout of the guest screens can be adjusted as needed using the tools which come with the guest operating system.</p>
     10    <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions includes drivers for X.Org. You should not need to change these. By default these drivers are in the following directory: </p>
     11    <p><filepath>/opt/VBoxGuestAdditions-<varname>version</varname>/other/</filepath></p>
     12    <p>The correct versions for the X server are symbolically linked into the X.Org driver directories.</p>
     13    <p>For graphics integration to work correctly, the X server must load the <codeph>vboxvideo</codeph> driver. Many recent X server versions look for it automatically if they see that they are running in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. For an optimal user experience, the guest kernel drivers must be loaded and the Guest Additions tool <userinput>VBoxClient</userinput> must be running as a client in the X session.</p>
     14    <p>For mouse integration to work correctly, the guest kernel drivers must be loaded. In addition, for legacy X servers the correct <codeph>vboxmouse</codeph> driver must be loaded and associated with <filepath>/dev/mouse</filepath> or <filepath>/dev/psaux</filepath>. For most guests, a driver for a PS/2 mouse must be loaded and the correct vboxmouse driver must be associated with <filepath>/dev/vboxguest</filepath>.</p>
     15    <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> guest graphics driver can use any graphics configuration for which the virtual resolution fits into the virtual video memory allocated to the virtual machine, minus a small amount used by the guest driver, as described in <xref href="settings-display.dita">Display Settings</xref>. The driver will offer a range of standard modes at least up to the default guest resolution for all active guest monitors. The default mode can be changed by setting the output property VBOX_MODE to "&lt;width&gt;x&lt;height&gt;" for any guest monitor. When VBoxClient and the kernel drivers are active this is done automatically when the host requests a mode change. The driver for older versions can only receive new modes by querying the host for requests at regular intervals. </p>
     16    <p>With legacy X Servers before version 1.3, you can also add your own modes to the X server configuration file. Add them to the "Modes" list in the "Display" subsection of the "Screen" section. For example, the following section has a custom 2048x800 resolution mode added: </p>
     17    <pre xml:space="preserve">Section "Screen"
     18        Identifier    "Default Screen"
     19        Device        "VirtualBox graphics card"
     20        Monitor       "Generic Monitor"
     21        DefaultDepth  24
     22        SubSection "Display"
     23                Depth         24
     24                Modes         "2048x800" "800x600" "640x480"
     25        EndSubSection
     26EndSection</pre>
    5427  </body>
    5528 

  • trunk/doc/manual/en_US/dita/topics/additions-linux-install.dita

    r99797 r108796  
    55 
    66  <body>
    7     <p>
    8           The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions for Linux are provided on
    9           the same virtual CD-ROM file as the Guest Additions for
    10           Windows. See <xref href="mountingadditionsiso.dita#mountingadditionsiso"/>. They also
    11           come with an installation program that guides you through the
    12           setup process. However, due to the significant differences
    13           between Linux distributions, installation may be slightly more
    14           complex when compared to Windows.
    15         </p>
    16     <p>
    17           Installation generally involves the following steps:
    18         </p>
     7    <p>To install the guest additions:</p>
    198    <ol>
    209      <li>
    21         <p>
    22               Before installing the Guest Additions, you prepare your
    23               guest system for building external kernel modules. This
    24               works as described in
    25               <xref href="externalkernelmodules.dita#externalkernelmodules"/>, except that this
    26               step must be performed in your Linux
    27               <i>guest</i> instead of on a Linux host
    28               system.
    29             </p>
    30         <p>
    31               If you suspect that something has gone wrong, check that
    32               your guest is set up correctly and run the following
    33               command as root:
    34             </p>
    35         <pre xml:space="preserve">rcvboxadd setup</pre>
     10        <p>Prepare your guest system for building external kernel modules. Follow the steps in <xref href="externalkernelmodules.dita#externalkernelmodules"/>, on your Linux VM instead of on a Linux host system.</p>
    3611      </li>
    3712      <li>
    38         <p>
    39               Insert the <filepath>VBoxGuestAdditions.iso</filepath> CD
    40               file into your Linux guest's virtual CD-ROM drive, as
    41               described for a Windows guest in
    42               <xref href="mountingadditionsiso.dita#mountingadditionsiso"/>.
    43             </p>
     13        <p>Insert the <filepath>VBoxGuestAdditions.iso</filepath> CD file into your Linux guest's virtual CD-ROM drive. See <xref href="guestadd-install.dita"/>.</p>
    4414      </li>
    4515      <li>
    46         <p>
    47               Change to the directory where your CD-ROM drive is mounted
    48               and run the following command as root:
    49             </p>
     16        <p>Change to the directory where your CD-ROM drive is mounted and run the following command as root:</p>
    5017        <pre xml:space="preserve">sh ./VBoxLinuxAdditions.run</pre>
     18      </li>
     19      <li>
     20        <p>If you suspect that something has gone wrong, check that your VM is set up correctly and run the following command as root:<pre xml:space="preserve">rcvboxadd setup</pre></p>
    5121      </li>
    5222    </ol>

  • trunk/doc/manual/en_US/dita/topics/additions-linux-uninstall.dita

    r105388 r108796  
    55 
    66  <body>
    7     <p>If you have a version of the Guest Additions installed on your virtual machine and want to remove it without
    8       installing new ones, you can do so by inserting the Guest Additions CD image into the virtual CD-ROM drive as
    9       described above. Then run the installer for the current Guest Additions with the <codeph>uninstall</codeph>
    10       parameter from the path that the CD image is mounted on in the guest, as follows: </p>
     7    <p>If you have a version of the Guest Additions installed on your virtual machine and want to remove it without installing new ones, you can do so by inserting the Guest Additions CD image into the virtual CD-ROM drive as described in <xref href="guestadd-install.dita"/>. Then run the installer for the current Guest Additions with the <codeph>uninstall</codeph> parameter from the path that the CD image is mounted on in the guest, as follows:</p>
    118    <pre xml:space="preserve">sh ./VBoxLinuxAdditions.run uninstall</pre>
    12     <p>While this will normally work without issues, you may need to do some manual cleanup of the guest in some cases,
    13       especially of the XFree86Config or xorg.conf file. In particular, if the Additions version installed or the guest
    14       operating system were very old, or if you made your own changes to the Guest Additions setup after you installed
    15       them. </p>
    16     <p>You can uninstall the Additions as follows: </p>
     9    <p>While this will normally work without issues, you may need to do some manual cleanup of the guest in some cases, especially of the XFree86Config or xorg.conf file. In particular, if the Additions version installed or the guest operating system were very old, or if you made your own changes to the Guest Additions setup after you installed them.</p>
     10    <p>You can uninstall the Additions as follows:</p>
    1711    <pre xml:space="preserve">/opt/VBoxGuestAdditions-<varname>version</varname>/uninstall.sh</pre>
    18     <p>Replace <filepath>/opt/VBoxGuestAdditions-<varname>version</varname></filepath> with the correct Guest Additions
    19       installation directory. </p>
     12    <p>Where <filepath>/opt/VBoxGuestAdditions-<varname>version</varname></filepath> is the Guest Additions installation directory.</p>
    2013  </body>
    2114 

  • trunk/doc/manual/en_US/dita/topics/additions-linux-updating.dita

    r105388 r108796  
    55 
    66  <body>
    7     <p>The Guest Additions can simply be updated by going through the installation procedure again with an updated
    8       CD-ROM image. This will replace the drivers with updated versions. You should reboot after updating the Guest
    9       Additions. </p>
     7    <p>The Guest Additions can simply be updated by going through the installation procedure again with an updated CD-ROM image. This will replace the drivers with updated versions. You should reboot after updating the Guest Additions.</p>
     8    <p>Some Linux distributions already come with all or part of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions. You may choose to keep the distribution's version of the Guest Additions but these are often out of date and limited in functionality, so we recommend replacing them with the Guest Additions that come with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.</p>
     9    <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Linux Guest Additions installer tries to detect an existing installation and replace them but depending on how the distribution integrates the Guest Additions, this may require some manual interaction. Take a snapshot of the virtual machine before replacing preinstalled Guest Additions.</p>
    1010  </body>
    1111 

  • trunk/doc/manual/en_US/dita/topics/additions-linux.dita

    r105134 r108796  
    11<?xml version='1.0' encoding='UTF-8'?>
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    3 <topic xml:lang="en-us" id="additions-linux">
     3<topic xml:lang="en-us" id="ct_additions-linux">
    44  <title>Guest Additions for Linux</title>
    5  
    65  <body>
    7     <p>
    8         Like the Windows Guest Additions, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest
    9         Additions for Linux are a set of device drivers and system
    10         applications which may be installed in the guest operating
    11         system.
    12       </p>
    13     <p>
    14         The following Linux distributions are officially supported:
    15       </p>
    16     <ul>
    17       <li>
    18         <p>
    19             Oracle Linux as of version 5, including UEK kernels
    20           </p>
    21       </li>
    22       <li>
    23         <p>
    24             Fedora as of Fedora Core 4
    25           </p>
    26       </li>
    27       <li>
    28         <p>
    29             Red Hat Enterprise Linux as of version 3
    30           </p>
    31       </li>
    32       <li>
    33         <p>
    34             SUSE and openSUSE Linux as of version 9
    35           </p>
    36       </li>
    37       <li>
    38         <p>
    39             Ubuntu as of version 5.10
    40           </p>
    41       </li>
    42     </ul>
    43     <p>
    44         Many other distributions are known to work with the Guest
    45         Additions.
    46       </p>
    47     <p>
    48         The version of the Linux kernel supplied by default in SUSE and
    49         openSUSE 10.2, Ubuntu 6.10 (all versions) and Ubuntu 6.06
    50         (server edition) contains a bug which can cause it to crash
    51         during startup when it is run in a virtual machine. The Guest
    52         Additions work in those distributions.
    53       </p>
    54     <p> Note that some Linux distributions already come with all or part of the <ph
    55         conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions. You may choose to keep
    56       the distribution's version of the Guest Additions but these are often out of date and limited
    57       in functionality, so we recommend replacing them with the Guest Additions that come with <ph
    58         conkeyref="vbox-conkeyref-phrases/product-name"/>. The <ph
    59         conkeyref="vbox-conkeyref-phrases/product-name"/> Linux Guest Additions installer tries to
    60       detect an existing installation and replace them but depending on how the distribution
    61       integrates the Guest Additions, this may require some manual interaction. It is highly
    62       recommended to take a snapshot of the virtual machine before replacing preinstalled Guest
    63       Additions. </p>
     6    <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions for Linux are a set of device drivers and system applications that may be installed in the guest operating system. The Linux Guest Additions will run on VMs running these versions of Linux. See also <xref href="host-guest-matrix.dita"/>.</p>
     7    <section>
     8      <title>Arm64 VMs</title>
     9      <ul>
     10        <li>
     11          <p>Oracle Linux 8 and later, including UEK kernels</p>
     12        </li>
     13      </ul>
     14    </section>
     15    <section>
     16      <title>x86 and x86_64 VMs</title>
     17      <ul>
     18        <li>
     19          <p>Oracle Linux 5 and later, including UEK kernels</p>
     20        </li>
     21        <li>
     22          <p>Fedora Core 4 and later</p>
     23        </li>
     24        <li>
     25          <p>Red Hat Enterprise Linux version 3 and later</p>
     26        </li>
     27        <li>
     28          <p>SUSE and openSUSE Linux version 9 and later</p>
     29        </li>
     30        <li>
     31          <p>Ubuntu version 5.10 and later</p>
     32        </li>
     33      </ul>
     34    </section>
     35    <p>The guest additions may also work on other distributions.</p>
    6436  </body>
    6537</topic>

  • trunk/doc/manual/en_US/dita/topics/additions-os2.dita

    r107390 r108796  
    55 
    66  <body>
    7     <p>
    8       <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also ships with a set of drivers that improve running OS/2 in a virtual machine. Due to restrictions of OS/2 itself, this variant of the Guest Additions has a limited feature set. Specifically, seamless windows and automatic guest resizing are not implemented in Guest Additions for OS/2 because of inherent limitations of the OS/2 graphics system.</p>
    9     <p>
    10         The OS/2 Guest Additions are provided on the same ISO CD-ROM as
    11         those for the other platforms. Mount the ISO in OS/2 as
    12         described previously. The OS/2 Guest Additions are located in
    13         the directory <filepath>\OS2</filepath>.
    14       </p>
    15     <p>
    16         We do not provide an automatic installer at this time. See the
    17         <filepath>readme.txt</filepath> file in the CD-ROM directory,
    18         which describes how to install the OS/2 Guest Additions
    19         manually.
    20       </p>
     7    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> also includes a set of drivers that improve running OS/2 in a virtual machine. Due to restrictions of OS/2 itself, this variant of the Guest Additions has a limited feature set. Specifically, seamless windows and automatic guest resizing are not implemented in Guest Additions for OS/2 because of inherent limitations of the OS/2 graphics system.</p>
     8    <p>The OS/2 Guest Additions are provided on the same ISO CD-ROM as those for the other platforms. Mount the ISO in OS/2 as described in <xref href="guestadd-install.dita"/>. The OS/2 Guest Additions are located in the directory <filepath>\OS2</filepath>.</p>
     9    <p>We do not provide an automatic installer. See the <filepath>readme.txt</filepath> file in the CD-ROM directory, which describes how to install the OS/2 Guest Additions manually.</p>
    2110  </body>
    2211 

  • trunk/doc/manual/en_US/dita/topics/additions-solaris-install.dita

    r99797 r108796  
    55 
    66  <body>
    7     <p>
    8           The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions for Oracle Solaris are
    9           provided on the same ISO CD-ROM as the Additions for Windows
    10           and Linux. They come with an installation program that guides
    11           you through the setup process.
    12         </p>
    13     <p>
    14           Installation involves the following steps:
    15         </p>
    16     <ol>
    17       <li>
    18         <p>
    19               Mount the <filepath>VBoxGuestAdditions.iso</filepath> file
    20               as your Oracle Solaris guest's virtual CD-ROM drive,
    21               exactly the same way as described for a Windows guest in
    22               <xref href="mountingadditionsiso.dita#mountingadditionsiso"/>.
    23             </p>
    24         <p>
    25               If the CD-ROM drive on the guest does not get mounted, as
    26               seen with some versions of Oracle Solaris 10, run the
    27               following command as root:
    28             </p>
    29         <pre xml:space="preserve">svcadm restart volfs</pre>
    30       </li>
    31       <li>
    32         <p>
    33               Change to the directory where your CD-ROM drive is mounted
    34               and run the following command as root:
    35             </p>
    36         <pre xml:space="preserve">pkgadd -G -d ./VBoxSolarisAdditions.pkg</pre>
    37       </li>
    38       <li>
    39         <p>
    40               Choose <b outputclass="bold">1</b> and confirm
    41               installation of the Guest Additions package. After the
    42               installation is complete, log out and log in to X server
    43               on your guest, to activate the X11 Guest Additions.
    44             </p>
    45       </li>
    46     </ol>
     7    <p>Follow the steps in <xref href="guestadd-install.dita"/>.</p>
     8    <p>If the CD-ROM drive on the guest does not get mounted, as seen with some versions of Oracle Solaris 10, run the following command as root: <pre xml:space="preserve">svcadm restart volfs</pre></p>
     9    <p>Change to the directory where your CD-ROM drive is mounted and run the following command as root: <pre xml:space="preserve">pkgadd -G -d ./VBoxSolarisAdditions.pkg</pre></p>
     10    <p>Choose <b outputclass="bold">1</b> and confirm installation of the Guest Additions package. After the installation is complete, log out and log in to X server on your guest, to activate the X11 Guest Additions.</p>
    4711  </body>
    4812 

  • trunk/doc/manual/en_US/dita/topics/additions-solaris-uninstall.dita

    r98549 r108796  
    55 
    66  <body>
    7     <p>
    8           The Oracle Solaris Guest Additions can be safely removed by
    9           removing the package from the guest. Open a root terminal
    10           session and run the following command:
    11         </p>
     7    <p>The Oracle Solaris Guest Additions can be safely removed by removing the package from the guest. Open a root terminal session and run the following command:</p>
    128    <pre xml:space="preserve">pkgrm SUNWvboxguest</pre>
    139  </body>

  • trunk/doc/manual/en_US/dita/topics/additions-solaris-updating.dita

    r98549 r108796  
    55 
    66  <body>
    7     <p>
    8           The Guest Additions should be updated by first uninstalling
    9           the existing Guest Additions and then installing the new ones.
    10           Attempting to install new Guest Additions without removing the
    11           existing ones is not possible.
    12         </p>
     7    <p>The Guest Additions should be updated by first uninstalling the existing Guest Additions and then installing the new ones. Attempting to install new Guest Additions without removing the existing ones is not possible.</p>
    138  </body>
    149 

  • trunk/doc/manual/en_US/dita/topics/additions-solaris.dita

    r99797 r108796  
    55 
    66  <body>
    7     <p>
    8         Like the Windows Guest Additions, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest
    9         Additions for Oracle Solaris take the form of a set of device
    10         drivers and system applications which may be installed in the
    11         guest operating system.
    12       </p>
    13     <p>
    14         The following Oracle Solaris distributions are officially
    15         supported:
    16       </p>
     7    <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions for Oracle Solaris take the form of a set of device drivers and system applications which may be installed in the guest operating system.</p>
     8    <p>The Solaris Guest Additions will run on VMs running these versions of Solaris. See also <xref href="host-guest-matrix.dita"/>.</p>
    179    <ul>
    1810      <li>
    19         <p>
    20             Oracle Solaris 11, including Oracle Solaris 11 Express
    21           </p>
     11        <p>Oracle Solaris 11, including Oracle Solaris 11 Express</p>
    2212      </li>
    2313      <li>
    24         <p>
    25             Oracle Solaris 10 4/08 and later
    26           </p>
     14        <p>Oracle Solaris 10 4/08 and later</p>
    2715      </li>
    2816    </ul>
    29     <p>
    30         Other distributions may work if they are based on comparable
    31         software releases.
    32       </p>
     17    <p>The Guest Additions may work with other distributions that are based on comparable software releases.</p>
    3318  </body>
    3419</topic>

  • trunk/doc/manual/en_US/dita/topics/additions-windows-install-unattended-certs.dita

    r108599 r108796  
    55 
    66  <body>
    7     <p>To avoid popups when performing an unattended installation of the <ph
    8         conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions, the code signing certificates used to sign
    9       the drivers needs to be installed in the correct certificate stores on the guest operating system. Failure to do
    10       this will cause a typical Windows installation to display multiple dialogs asking whether you want to install a
    11       particular driver. </p>
     7    <p>To avoid popups when performing an unattended installation of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions, the code signing certificates used to sign the drivers needs to be installed in the correct certificate stores on the guest operating system. If you do not do this, the installation will prompt you before the installation of each driver.</p>
     8    <p>The certificates are stored for you if installing Guest Additions as part of the Windows unattended installation when creating a new VM. If you are automating the installation of Guest Additions yourself, you first need to install the code signing certificates on the VM.</p>
     9    <p>Use the <filepath>VBoxCertUtil.exe</filepath> utility from the <filepath>cert</filepath> folder on the Guest Additions installation CD.</p>
    1210    <note>
    13       <p>On some legacy Windows versions, such as Windows 2000 and Windows XP, the user intervention popups mentioned
    14         above are always displayed, even after importing the Oracle certificates. </p>
     11      <p>On some legacy Windows versions, such as Windows 2000 and Windows XP, the user intervention popups mentioned above are always displayed, even after importing the Oracle certificates.</p>
    1512    </note>
    16     <p>Installing the code signing certificates on a Windows guest can be done automatically. Use the
    17         <filepath>VBoxCertUtil.exe</filepath> utility from the <filepath>cert</filepath> folder on the Guest Additions
    18       installation CD. </p>
    19     <p>Use the following steps: </p>
    2013    <ol>
    2114      <li>
    22         <p>
    23                 Log in as Administrator on the guest.
    24               </p>
     15        <p>Log in as Administrator on the guest.</p>
    2516      </li>
    2617      <li>
    27         <p>
    28                 Mount the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions .ISO.
    29               </p>
     18        <p>Mount the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions ISO.</p>
    3019      </li>
    3120      <li>
    32         <p>
    33                 Open a command line window on the guest and change to
    34                 the <filepath>cert</filepath> folder on the
    35                 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions CD.
    36               </p>
     21        <p>Open a command line window on the guest and change to the <filepath>cert</filepath> folder on the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions CD.</p>
    3722      </li>
    3823      <li>
    39         <p>
    40                 Run the following command:
    41               </p>
     24        <p>Run the following command:</p>
    4225        <pre xml:space="preserve">VBoxCertUtil.exe add-trusted-publisher vbox*.cer --root vbox*.cer</pre>
    43         <p>
    44                 This command installs the certificates to the
    45                 certificate store. When installing the same certificate
    46                 more than once, an appropriate error will be displayed.
    47               </p>
     26        <p>This command installs the certificates to the certificate store. When installing the same certificate more than once, an appropriate error will be displayed.</p>
    4827      </li>
    4928    </ol>
    50     <p>To allow for completely unattended guest installations, you can specify a command line parameter to the install
    51       launcher: </p>
    52     <pre xml:space="preserve">VBoxWindowsAdditions.exe /S</pre>
    53     <p>This automatically installs the right files and drivers for the corresponding platform, either 32-bit or 64-bit.</p>
    54     <note>
    55       <p>For Windows Aero to run correctly on a guest, the guest's VRAM size needs to be configured to at least 128 MB.</p>
    56     </note>
    57     <p>For more options regarding unattended guest installations, consult the command line help by using the command:</p>
    58     <pre xml:space="preserve">VBoxWindowsAdditions.exe /?</pre>
    5929  </body>
    6030 

  • trunk/doc/manual/en_US/dita/topics/additions-windows-updating.dita

    r99797 r108796  
    55 
    66  <body>
    7     <p>
    8           Windows Guest Additions can be updated by running the
    9           installation program again. This replaces the previous
    10           Additions drivers with updated versions.
    11         </p>
    12     <p>
    13           Alternatively, you can also open the Windows Device Manager
    14           and select <b outputclass="bold">Update Driver...</b>
    15           for the following devices:
    16         </p>
     7    <p>Windows Guest Additions can be updated by running the installation program again. This replaces the previous Additions drivers with updated versions.</p>
     8    <p>Alternatively, you can also open the Windows Device Manager and select <b outputclass="bold">Update Driver...</b> for the following devices:</p>
    179    <ul>
    1810      <li>
    19         <p>
    20               <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Graphics Adapter
    21             </p>
     11        <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Graphics Adapter</p>
    2212      </li>
    2313      <li>
    24         <p>
    25               <ph conkeyref="vbox-conkeyref-phrases/product-name"/> System Device
    26             </p>
     14        <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> System Device</p>
    2715      </li>
    2816    </ul>
    29     <p>
    30           For each, choose the option to provide your own driver, click
    31           <b outputclass="bold">Have Disk</b> and navigate to the
    32           CD-ROM drive with the Guest Additions.
    33         </p>
     17    <p>For each, choose the option to provide your own driver, click <b outputclass="bold">Have Disk</b> and navigate to the CD-ROM drive with the Guest Additions.</p>
    3418  </body>
    3519 

  • trunk/doc/manual/en_US/dita/topics/additions-windows.dita

    r105388 r108796  
    11<?xml version='1.0' encoding='UTF-8'?>
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    3 <topic xml:lang="en-us" id="additions-windows">
     3<topic xml:lang="en-us" id="ct_additions-windows">
    44  <title>Guest Additions for Windows</title>
    5  
    65  <body>
    7     <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Windows Guest Additions are designed to be installed in
    8       a virtual machine running a Windows operating system. The following versions of Windows guests are supported: </p>
    9     <ul>
    10       <li>
    11         <p>
    12             Microsoft Windows 11
    13           </p>
    14       </li>
    15       <li>
    16         <p>
    17             Microsoft Windows Server 2022
    18           </p>
    19       </li>
    20       <li>
    21         <p>
    22             Microsoft Windows 10 (all builds)
    23           </p>
    24       </li>
    25       <li>
    26         <p>
    27             Microsoft Windows Server 2019
    28           </p>
    29       </li>
    30       <li>
    31         <p>
    32             Microsoft Windows Server 2016
    33           </p>
    34       </li>
    35       <li>
    36         <p>
    37             Microsoft Windows 8.1 (all editions)
    38           </p>
    39       </li>
    40       <li>
    41         <p>
    42             Microsoft Windows Server 2012R2
    43           </p>
    44       </li>
    45       <li>
    46         <p>
    47             Microsoft Windows 8 (all editions)
    48           </p>
    49       </li>
    50       <li>
    51         <p>
    52             Microsoft Windows Server 2012
    53           </p>
    54       </li>
    55       <li>
    56         <p>
    57             Microsoft Windows 7 (all editions)
    58           </p>
    59       </li>
    60       <li>
    61         <p>
    62             Microsoft Windows Server 2008R2
    63           </p>
    64       </li>
    65       <li>
    66         <p>
    67             Microsoft Windows Vista (all editions)
    68           </p>
    69       </li>
    70       <li>
    71         <p>
    72             Microsoft Windows Server 2008
    73           </p>
    74       </li>
    75       <li>
    76         <p>
    77             Microsoft Windows XP (any service pack)
    78           </p>
    79       </li>
    80       <li>
    81         <p>
    82             Microsoft Windows Server 2003 (any service pack)
    83           </p>
    84       </li>
    85       <li>
    86         <p>
    87             Microsoft Windows 2000 (any service pack)
    88           </p>
    89       </li>
    90       <li>
    91         <p>
    92             Microsoft Windows NT 4.0 (any service pack)
    93           </p>
    94       </li>
    95     </ul>
     6    <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Windows Guest Additions are designed to be installed in a virtual machine running a Windows operating system. The Windows Guest Additions will run on VMs running these versions of Windows. See also <xref href="host-guest-matrix.dita"/>.</p>
     7    <section>
     8      <title>Arm64 VMs</title>
     9      <ul>
     10        <li>
     11          <p>Microsoft Windows 11</p>
     12        </li>
     13      </ul>
     14    </section>
     15    <section>
     16      <title>x86 and x86_64 VMs</title>
     17      <ul>
     18        <li>
     19          <p>Microsoft Windows 11</p>
     20        </li>
     21        <li>
     22          <p>Microsoft Windows Server 2022</p>
     23        </li>
     24        <li>
     25          <p>Microsoft Windows 10 (all builds)</p>
     26        </li>
     27        <li>
     28          <p>Microsoft Windows Server 2019</p>
     29        </li>
     30        <li>
     31          <p>Microsoft Windows Server 2016</p>
     32        </li>
     33        <li>
     34          <p>Microsoft Windows 8.1 (all editions)</p>
     35        </li>
     36        <li>
     37          <p>Microsoft Windows Server 2012R2</p>
     38        </li>
     39        <li>
     40          <p>Microsoft Windows 8 (all editions)</p>
     41        </li>
     42        <li>
     43          <p>Microsoft Windows Server 2012</p>
     44        </li>
     45        <li>
     46          <p>Microsoft Windows 7 (all editions)</p>
     47        </li>
     48        <li>
     49          <p>Microsoft Windows Server 2008R2</p>
     50        </li>
     51        <li>
     52          <p>Microsoft Windows Vista (all editions)</p>
     53        </li>
     54        <li>
     55          <p>Microsoft Windows Server 2008</p>
     56        </li>
     57        <li>
     58          <p>Microsoft Windows XP (any service pack)</p>
     59        </li>
     60        <li>
     61          <p>Microsoft Windows Server 2003 (any service pack)</p>
     62        </li>
     63        <li>
     64          <p>Microsoft Windows 2000 (any service pack)</p>
     65        </li>
     66        <li>
     67          <p>Microsoft Windows NT 4.0 (any service pack)</p>
     68        </li>
     69      </ul>
     70    </section>
    9671  </body>
    9772</topic>

  • trunk/doc/manual/en_US/dita/topics/autologon.dita

    r105335 r108796  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="autologon">
    4   <title>Automated Guest Logins</title>
     4  <title><?oxy_comment_start author="Mhari Duncan" timestamp="20250326T171726+0000" comment="Consider putting this somewhere related to automating access. Remote access chapter? If changing it from only remote access to other access methods?"?>Automated Guest Logins<?oxy_comment_end?></title>
    55 
    66  <body>

  • trunk/doc/manual/en_US/dita/topics/guest-os.dita

    r108297 r108796  
    66  <body>
    77    <p>You can run most operating systems (OSs) successfully on a virtual machine (VM) in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
    8     <p>However, to achieve near-native performance of the guest code on your machine, some optimizations that are specific to certain OSs had to be made. So while your favorite OS <i>may</i> run as a guest, Oracle provides guest additions and premier support only for selected OSs.</p>
     8    <p>However, to achieve near-native performance of the guest code on your machine, some optimizations that are specific to certain OSs had to be made. So while your favorite OS <i>may</i> run as a guest, Oracle provides premier support only for selected OSs and guest additions.</p>
    99    <p>Other guest OSs can be used with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, but only qualify for limited support. Therefore, resolution of customer issues for such guest OSs cannot be assured.</p>
    1010    <p>The virtual hardware determines the choice of guest OSs available, as does the host machine. Ensure you take all aspects of VM configuration into consideration when creating a VM.</p>

  • trunk/doc/manual/en_US/dita/topics/guestadd-install.dita

    r105289 r108796  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="guestadd-install">
    4   <title>Installing and Maintaining Guest Additions</title>
     4  <title>Installing Guest Additions</title>
    55 
    66  <body>
    7     <p>Guest Additions are available for virtual machines running Windows, Linux, Oracle Solaris, or OS/2. The following
    8       sections describe the specifics of each variant in detail. </p>
     7    <p>These instructions apply to all OSs. For additional information, see <xref href="additions-windows.dita"/>, <xref href="additions-linux.dita"/>, <xref href="additions-solaris.dita"/>, or <xref href="additions-os2.dita"/>.</p>
     8    <section>
     9      <title>Mount the Guest Additions ISO</title>
     10      <ol>
     11        <li>
     12          <p>Start the virtual machine. The OS must be installed.</p>
     13        </li>
     14        <li>
     15          <p>From the <uicontrol>Devices</uicontrol> menu, choose <uicontrol>Insert Guest Additions CD Image</uicontrol>, which mounts the Guest Additions ISO file inside your VM.</p>
     16        </li>
     17        <li>
     18          <p>If this option is not available, or if you prefer to mount the ISO manually:</p>
     19          <ol>
     20            <li>
     21              <p>From the <uicontrol>Devices</uicontrol> menu, choose <uicontrol>Optical Drives</uicontrol>, and then<uicontrol> Choose/Create a Disk Image</uicontrol>. This displays the <xref href="virtual-media-manager.dita#virtual-media-manager"/>.</p>
     22            </li>
     23            <li>
     24              <p>In the Virtual Media Manager, click <uicontrol>Add</uicontrol> and browse your host file system for the <filepath>VBoxGuestAdditions.iso</filepath> file.</p>
     25              <ul>
     26                <li>On a Windows host, this file is in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installation directory, usually in <filepath>C:\Program files\Oracle\VirtualBox</filepath>.</li>
     27                <li>
     28                  <p>On a Linux host, this file is in the <filepath>additions</filepath> folder where you installed <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, usually <filepath>/opt/VirtualBox/</filepath>.</p>
     29                </li>
     30                <li>
     31                  <p>On Oracle Solaris hosts, this file is in the <filepath>additions</filepath> folder where you installed <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, usually <filepath>/opt/VirtualBox</filepath>.</p>
     32                </li>
     33              </ul>
     34            </li>
     35            <li>
     36              <p>In the Virtual Media Manager, select the ISO file and click <uicontrol>Add</uicontrol>. This mounts the ISO file and presents it to your guest OS as a CD-ROM.</p>
     37            </li>
     38          </ol>
     39        </li>
     40      </ol>
     41    </section>
     42    <section>
     43      <title>Run the Guest Additions Installer</title>
     44      <ol>
     45        <li>
     46          <p>Mount the ISO as described in the previous task.</p>
     47        </li>
     48        <li>
     49          <p>Unless you have the Autostart feature disabled, or it is not supported, the OS will now autostart the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions installer from the Guest Additions ISO.</p>
     50          <p>If the Autostart feature has been turned off, choose <filepath>VBox&lt;OS>Additions.exe</filepath> from the CD/DVD drive inside the guest to start the installer, where <filepath>&lt;OS></filepath> is <filepath>Windows</filepath>, <filepath>Linux</filepath>, <filepath>OS2</filepath> or <filepath>Solaris</filepath>.</p>
     51        </li>
     52        <li>
     53          <p>Follow the instructions in the installer.</p>
     54        </li>
     55        <li>
     56          <p>Reboot the guest OS.</p>
     57        </li>
     58      </ol>
     59    </section>
    960  </body>
    1061</topic>

  • trunk/doc/manual/en_US/dita/topics/guestadd-intro.dita

    r108599 r108796  
    55 
    66  <body>
    7     <p>The Guest Additions are designed to be installed <i>inside</i> a virtual machine after the guest operating system has been installed. They consist of device drivers and system applications that optimize the guest operating system for better performance and usability. See <xref href="guest-os.dita"/> for details on what guest operating systems are fully supported with Guest Additions by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.</p>
    8     <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions for all supported guest operating
    9       systems are provided as a single CD-ROM image file which is called <filepath>VBoxGuestAdditions.iso</filepath>.
    10       This image file is located in the installation directory of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    11       To install the Guest Additions for a particular VM, you mount this ISO file in your VM as a virtual CD-ROM and
    12       install from there. </p>
    13     <p>The Guest Additions offer the following features: </p>
     7    <p>The Guest Additions offer the following features:</p>
    148    <ul>
    159      <li>
    16         <p><b outputclass="bold">Mouse pointer integration</b>. To
    17           overcome the limitations for mouse support described in
    18           <xref href="keyb_mouse_normal.dita#keyb_mouse_normal"/>, this feature provides
    19           you with seamless mouse support. You will only have one mouse
    20           pointer and pressing the Host key is no longer required to
    21           <i>free</i> the mouse from being captured by the
    22           guest OS. To make this work, a special mouse driver is
    23           installed in the guest that communicates with the physical
    24           mouse driver on your host and moves the guest mouse pointer
    25           accordingly.
    26         </p>
     10        <p><b outputclass="bold">Mouse pointer integration</b>. To overcome the limitations for mouse support described in <xref href="keyb_mouse_normal.dita#keyb_mouse_normal"/>, this feature provides you with seamless mouse support. You will only have one mouse pointer and pressing the Host key is no longer required to <i>free</i> the mouse from being captured by the guest OS. To make this work, a special mouse driver is installed in the guest that communicates with the physical mouse driver on your host and moves the guest mouse pointer accordingly.</p>
    2711      </li>
    2812      <li>
    29         <p><b outputclass="bold">Shared folders.</b> These provide
    30           an easy way to exchange files between the host and the guest.
    31           Much like ordinary Windows network shares, you can tell
    32           <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to treat a certain host directory as a shared
    33           folder, and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will make it available to the guest
    34           operating system as a network share, irrespective of whether
    35           the guest actually has a network. See
    36           <xref href="sharedfolders.dita#sharedfolders"/>.
    37         </p>
     13        <p><b outputclass="bold">Shared folders.</b> These provide an easy way to exchange files between the host and the guest. Much like ordinary Windows network shares, you can tell <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to treat a certain host directory as a shared folder, and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will make it available to the guest operating system as a network share, irrespective of whether the guest actually has a network. See <xref href="sharedfolders.dita#sharedfolders"/>.</p>
    3814      </li>
    3915      <li>
    40         <p><b outputclass="bold">Better video support.</b> While the virtual graphics card which <ph
    41             conkeyref="vbox-conkeyref-phrases/product-name"/> emulates for any guest operating
    42           system provides all the basic features, the custom video drivers that are installed with
    43           the Guest Additions provide you with extra high and nonstandard video modes, as well as
    44           accelerated video performance. </p>
    45         <p>In addition, with Windows, Linux, and Oracle Solaris guests, you can resize the virtual machine's window if
    46           the Guest Additions are installed. The video resolution in the guest will be automatically adjusted, as if you
    47           had manually entered an arbitrary resolution in the guest's <b outputclass="bold">Display</b> settings. See
    48             <xref href="intro-resize-window.dita#intro-resize-window"/>. </p>
    49         <p>If the Guest Additions are installed, 3D graphics for guest applications can be accelerated. See <xref href="guestadd-video.dita#guestadd-video"/>. </p>
     16        <p><b outputclass="bold">Better video support.</b> While the virtual graphics card which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> emulates for any guest operating system provides all the basic features, the custom video drivers that are installed with the Guest Additions provide you with extra high and nonstandard video modes, as well as accelerated video performance.</p>
     17        <p>In addition, with Windows, Linux, and Oracle Solaris guests, you can resize the virtual machine's window if the Guest Additions are installed. The video resolution in the guest will be automatically adjusted, as if you had manually entered an arbitrary resolution in the guest's <b outputclass="bold">Display</b> settings. See <xref href="intro-resize-window.dita#intro-resize-window"/>.</p>
     18        <p>If the Guest Additions are installed, 3D graphics for guest applications can be accelerated. See <xref href="guestadd-video.dita#guestadd-video"/>.</p>
    5019      </li>
    5120      <li>
    52         <p><b outputclass="bold">Seamless windows.</b> With this
    53           feature, the individual windows that are displayed on the
    54           desktop of the virtual machine can be mapped on the host's
    55           desktop, as if the underlying application was actually running
    56           on the host. See <xref href="seamlesswindows.dita#seamlesswindows"/>.
    57         </p>
     21        <p><b outputclass="bold">Seamless windows.</b> With this feature, the individual windows that are displayed on the desktop of the virtual machine can be mapped on the host's desktop, as if the underlying application was actually running on the host. See <xref href="seamlesswindows.dita#seamlesswindows"/>.</p>
    5822      </li>
    5923      <li>
    60         <p><b outputclass="bold">Generic host/guest communication
    61           channels.</b> The Guest Additions enable you to control
    62           and monitor guest execution. The <i>guest
    63           properties</i> provide a generic string-based mechanism
    64           to exchange data bits between a guest and a host, some of
    65           which have special meanings for controlling and monitoring the
    66           guest. See <xref href="guestadd-guestprops.dita#guestadd-guestprops"/>.
    67         </p>
     24        <p><b outputclass="bold">Generic host/guest communication channels.</b> The Guest Additions enable you to control and monitor guest execution. The <i>guest properties</i> provide a generic string-based mechanism to exchange data bits between a guest and a host, some of which have special meanings for controlling and monitoring the guest. See <xref href="guestadd-guestprops.dita#guestadd-guestprops"/>.</p>
    6825        <p>Additionally, applications can be started in a guest from the host. See <xref
    6926            href="guestadd-guestcontrol.dita#guestadd-guestcontrol"/>. </p>
    7027      </li>
    7128      <li>
    72         <p><b outputclass="bold">Time synchronization.</b> With
    73           the Guest Additions installed, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can ensure that
    74           the guest's system time is better synchronized with that of
    75           the host.
    76         </p>
    77         <p>For various reasons, the time in the guest might run at a slightly different rate than the time on the host.
    78           The host could be receiving updates through NTP and its own time might not run linearly. A VM could also be
    79           paused, which stops the flow of time in the guest for a shorter or longer period of time. When the wall clock
    80           time between the guest and host only differs slightly, the time synchronization service attempts to gradually
    81           and smoothly adjust the guest time in small increments to either catch up or lose time. When the difference is
    82           too great, for example if a VM paused for hours or restored from saved state, the guest time is changed
    83           immediately, without a gradual adjustment. </p>
    84         <p>The Guest Additions will resynchronize the time regularly. See <xref href="changetimesync.dita">Tuning the
    85             Guest Additions Time Synchronization Parameters</xref> for how to configure the parameters of the time
    86           synchronization mechanism. </p>
     29        <p><b outputclass="bold">Time synchronization.</b> With the Guest Additions installed, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can ensure that the guest's system time is better synchronized with that of the host.</p>
     30        <p>For various reasons, the time in the guest might run at a slightly different rate than the time on the host. The host could be receiving updates through NTP and its own time might not run linearly. A VM could also be paused, which stops the flow of time in the guest for a shorter or longer period of time. When the wall clock time between the guest and host only differs slightly, the time synchronization service attempts to gradually and smoothly adjust the guest time in small increments to either catch up or lose time. When the difference is too great, for example if a VM paused for hours or restored from saved state, the guest time is changed immediately, without a gradual adjustment.</p>
     31        <p>The Guest Additions will resynchronize the time regularly. See <xref href="changetimesync.dita">Tuning the Guest Additions Time Synchronization Parameters</xref> for how to configure the parameters of the time synchronization mechanism.</p>
    8732      </li>
    8833      <li>
    89         <p><b outputclass="bold">Shared clipboard.</b> With the
    90           Guest Additions installed, the clipboard of the guest
    91           operating system can optionally be shared with your host
    92           operating system. See <xref href="generalsettings.dita"/>.
    93         </p>
     34        <p><b outputclass="bold">Shared clipboard.</b> With the Guest Additions installed, the clipboard of the guest operating system can optionally be shared with your host operating system. See <xref href="generalsettings.dita"/>.</p>
    9435      </li>
    9536      <li>
    96         <p><b outputclass="bold">Automated logins.</b> Also called
    97           credentials passing. See <xref href="autologon.dita">Automated Guest Logins</xref>.
    98         </p>
     37        <p><b outputclass="bold">Automated logins.</b> Also called credentials passing. See <xref href="autologon.dita">Automated Guest Logins</xref>.</p>
    9938      </li>
    10039    </ul>
    101     <p>Each version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, even minor releases, ship with their own
    102       version of the Guest Additions. While the interfaces through which the <ph
    103         conkeyref="vbox-conkeyref-phrases/product-name"/> core communicates with the Guest Additions are kept stable so
    104       that Guest Additions already installed in a VM should continue to work when <ph
    105         conkeyref="vbox-conkeyref-phrases/product-name"/> is upgraded on the host, for best results, it is recommended
    106       to keep the Guest Additions at the same version. </p>
    107     <p>The Windows and Linux Guest Additions therefore check automatically whether they have to be updated. If the host
    108       is running a newer <ph conkeyref="vbox-conkeyref-phrases/product-name"/> version than the Guest Additions, a
    109       notification with further instructions is displayed in the guest. </p>
    110     <p>To disable this update check for the Guest Additions of a given virtual machine, set the value of its
    111         <codeph>/VirtualBox/GuestAdd/CheckHostVersion</codeph> guest property to <codeph>0</codeph>. See <xref
    112         href="guestadd-guestprops.dita#guestadd-guestprops"/>. </p>
     40    <p>Each version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, even minor releases, include their own version of the Guest Additions. While the interfaces through which the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> core communicates with the Guest Additions are kept stable so that Guest Additions already installed in a VM should continue to work when <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is upgraded on the host, for best results you should keep the Guest Additions at the same version.</p>
     41    <p>The Windows and Linux Guest Additions therefore check automatically whether they have to be updated. If the host is running a newer <ph conkeyref="vbox-conkeyref-phrases/product-name"/> version than the Guest Additions, a notification with further instructions is displayed in the guest.</p>
     42    <p>To disable this update check for the Guest Additions of a given virtual machine, set the value of its <codeph>/VirtualBox/GuestAdd/CheckHostVersion</codeph> guest property to <codeph>0</codeph>. See <xref href="guestadd-guestprops.dita#guestadd-guestprops"/>.</p>
    11343  </body>
    11444 

  • trunk/doc/manual/en_US/dita/topics/guestadd-video.dita

    r108297 r108796  
    44  <title>Hardware-Accelerated Graphics</title>
    55  <body>
    6     <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions contain hardware 3D support for Windows, Linux, and Oracle Solaris guests.</p>
     6    <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions contain hardware 3D support for Windows, Linux, and Oracle Solaris guests. Video decoding acceleration is also used if the host can use it.</p>
    77    <p>With this feature, if an application inside your virtual machine uses 3D features through the OpenGL or Direct3D programming interfaces, instead of emulating them in software, which would be slow, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will attempt to use your host's 3D hardware. This works for all supported host platforms, provided that your host operating system can make use of your accelerated 3D hardware in the first place. The Guest Additions must be installed on your VM.</p>
    88    <p>The 3D acceleration feature is only available for certain Windows, Linux, and Oracle Solaris guests:</p>
    … …  
    1818      </li>
    1919    </ul>
     20    <p>The video decoding feature is available if the host is x86_64 running Windows or Linux, and the VM is 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>
     21    <p>On Linux hosts, you must have one of the following graphics drivers, with Vulkan 1.3 or later, to use video decoding:</p>
     22    <ul>
     23      <li>NVIDIA Linux Graphics Driver</li>
     24      <li>Mesa 3D Driver, for AMD and Intel graphics hardware</li>
     25    </ul>
     26    <p>Video decoding capabilities are disabled by default in Mesa 3D drivers (AMD and Intel), so you must set the following environment variables on the host:</p>
     27    <p>Intel: <codeph>export ANV_VIDEO_DECODE=1</codeph></p>
     28    <p>AMD: <codeph>export RADV_PERFTEST=video_decode</codeph></p>
    2029  </body>
    2130</topic>

  • trunk/doc/manual/en_US/dita/topics/guestadditions.dita

    r105289 r108796  
    55 
    66  <body>
    7     <p>The previous chapter covered getting started with <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and
    8       installing operating systems in a virtual machine. For any serious and interactive use, the <ph
    9         conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions will make your life much easier by providing
    10       closer integration between host and guest and improving the interactive performance of guest systems. This chapter
    11       describes the Guest Additions in detail. </p>
     7    <p>The Guest Additions are designed to be installed <i>inside</i> a virtual machine after the guest operating system has been installed. They consist of device drivers and system applications that optimize the guest operating system for better performance and usability. See <xref href="guest-os.dita"/> for details on the guest operating systems that Oracle provides premier support for.</p>
     8    <p>The available <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions are provided as a single CD-ROM image file called <filepath>VBoxGuestAdditions.iso</filepath>. This image file is located in the installation directory of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. To install the Guest Additions for a particular OS, you mount this ISO file in your VM as a virtual CD-ROM and install from there.</p>
     9    <p>You can also configure unattended installation of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions when you create a new VM. See <xref href="create-vm-unattended-install.dita"/>.</p>
    1210  </body>
    1311</topic>

  • trunk/doc/manual/en_US/dita/topics/host-guest-matrix.dita

    r107390 r108796  
    2323                    <tbody>
    2424                        <row>
    25                             <entry>x86-64 (for example Intel or AMD)</entry>
     25                            <entry>x86_64 (for example Intel or AMD)</entry>
    2626                            <entry>
    2727                                <p>Windows</p>
    … …  
    3131                                <p>Oracle Solaris</p>
    3232                            </entry>
    33                             <entry>x86 and x86-64</entry>
     33                            <entry>x86 and x86_64</entry>
    3434                            <entry>
    3535                                <p>Windows</p>

  • trunk/doc/manual/en_US/dita/topics/installation-packages.dita

    r107390 r108796  
    1414          </li>
    1515          <li>
    16             <p>Windows 11 with x86-64 processors</p>
     16            <p>Windows 11 with x86_64 processors</p>
    1717          </li>
    1818          <li>
    19             <p>Windows 10 with x86-64 processors</p>
     19            <p>Windows 10 with x86_64 processors</p>
    2020          </li>
    2121          <li>
    22             <p>Windows Server 2025 with x86-64 processors</p>
     22            <p>Windows Server 2025 with x86_64 processors</p>
    2323          </li>
    2424          <li>
    25             <p>Windows Server 2022 with x86-64 processors</p>
     25            <p>Windows Server 2022 with x86_64 processors</p>
    2626          </li>
    2727        </ul>
    … …  
    3232        <ul>
    3333          <li>
    34             <p>14 (Sonoma) with Intel x86-64 processors</p>
     34            <p>14 (Sonoma) with Intel x86_64 processors</p>
    3535          </li>
    3636          <li>
    37             <p>13 (Ventura) with Intel x86-64 processors</p>
     37            <p>13 (Ventura) with Intel x86_64 processors</p>
    3838          </li>
    3939          <li>
    40             <p>12 (Monterey) with Intel x86-64 processors</p>
     40            <p>12 (Monterey) with Intel x86_64 processors</p>
    4141          </li>
    4242          <li>
    43             <p>11 (Big Sur) with Intel x86-64 processors</p>
     43            <p>11 (Big Sur) with Intel x86_64 processors</p>
    4444          </li>
    4545        </ul>
    … …  
    6666        <p><b outputclass="bold">Linux Distributions</b>:</p>
    6767        <ul>
    68           <li><b>​Oracle Linux 9 / Red Hat Enterprise Linux 9</b> with x86-64 processors</li>
    69           <li><b>​Oracle Linux 8 / Red Hat Enterprise Linux 8​</b> with x86-64 processors</li>
    70           <li><b>Ubuntu 24.10</b>​ with x86-64 processors</li>
    71           <li><b>Ubuntu 24.04</b>​ with x86-64 processors</li>
    72           <li><b>Ubuntu 22.04</b> with x86-64 processors</li>
    73           <li><b>​Ubuntu 20.04​</b> with x86-64 processors</li>
    74           <li><b>Debian 12</b> - Debian GNU/Linux 12 (Bookworm)​ with x86-64 processors</li>
    75           <li><b>Debian 11</b> - Debian GNU/Linux 11 (Bullseye) with x86-64 processors</li>
    76           <li><b>​openSUSE 15.3 / 15.4 / 15.5 / 15.6</b> with x86-64 processors</li>
    77           <li><b>Fedora 40 / 41</b> with x86-64 processors</li>
    78           <li><b>​All distributions</b> with x86-64 processors - Built on EL6 and therefore not requiring recent system libraries. Not covered by Oracle Premier Support.</li>
     68          <li><b>​Oracle Linux 9 / Red Hat Enterprise Linux 9</b> with x86_64 processors</li>
     69          <li><b>​Oracle Linux 8 / Red Hat Enterprise Linux 8​</b> with x86_64 processors</li>
     70          <li><b>Ubuntu 24.10</b>​ with x86_64 processors</li>
     71          <li><b>Ubuntu 24.04</b>​ with x86_64 processors</li>
     72          <li><b>Ubuntu 22.04</b> with x86_64 processors</li>
     73          <li><b>​Ubuntu 20.04​</b> with x86_64 processors</li>
     74          <li><b>Debian 12</b> - Debian GNU/Linux 12 (Bookworm)​ with x86_64 processors</li>
     75          <li><b>Debian 11</b> - Debian GNU/Linux 11 (Bullseye) with x86_64 processors</li>
     76          <li><b>​openSUSE 15.3 / 15.4 / 15.5 / 15.6</b> with x86_64 processors</li>
     77          <li><b>Fedora 40 / 41</b> with x86_64 processors</li>
     78          <li><b>​All distributions</b> with x86_64 processors - Built on EL6 and therefore not requiring recent system libraries. Not covered by Oracle Premier Support.</li>
    7979        </ul>
    8080      </li>
    … …  
    8787        <ul>
    8888          <li>
    89             <p> Oracle Solaris 11.4 </p>
     89            <p> Oracle Solaris 11.4</p>
    9090          </li>
    9191        </ul>

  • trunk/doc/manual/en_US/dita/topics/mountingadditionsiso.dita

    r107390 r108796  
    55 
    66  <body>
    7     <p>In the <b outputclass="bold">Devices</b> menu in the virtual machine's menu bar, <ph
    8         conkeyref="vbox-conkeyref-phrases/product-name"/> has a menu item <b outputclass="bold">Insert Guest Additions
    9         CD Image</b>, which mounts the Guest Additions ISO file inside your virtual machine. A Windows guest should then
    10       automatically start the Guest Additions installer, which installs the Guest Additions on your Windows guest. </p>
    11     <p>For other guest operating systems, or if automatic start of software on a CD is disabled, you need to do a manual
    12       start of the installer. </p>
     7    <p>Follow the steps in <xref href="guestadd-install.dita"/>.</p>
    138    <note>
    14       <p>For the basic Direct3D acceleration to work in a Windows guest, you have to install the WDDM video driver
    15         available for Windows Vista or later. </p>
    16       <p> For Windows 8 and later, only the WDDM Direct3D video driver is available. For basic Direct3D acceleration to work in Windows XP guests, you have to install the Guest Additions in Safe Mode.</p>
     9      <p>For the basic Direct3D acceleration to work in a Windows guest, you have to install the WDDM video driver available for Windows Vista or later.</p>
     10      <p>For Windows 8 and later, only the WDDM Direct3D video driver is available.</p>
    1711    </note>
    18     <p>If you prefer to mount the Guest Additions manually, you can perform the following steps: </p>
    19     <ol>
    20       <li>
    21         <p>Start the virtual machine in which you have installed Windows. </p>
    22       </li>
    23       <li>
    24         <p>Select <b outputclass="bold">Optical Drives</b> from the <b outputclass="bold">Devices</b> menu in the
    25           virtual machine's menu bar and then <b outputclass="bold">Choose/Create a Disk Image</b>. This displays the
    26           Virtual Media Manager, described in <xref href="virtual-media-manager.dita#virtual-media-manager"/>. </p>
    27       </li>
    28       <li>
    29         <p>In the Virtual Media Manager, click <b outputclass="bold">Add</b> and browse your host file system for the
    30             <filepath>VBoxGuestAdditions.iso</filepath> file. </p>
    31         <ul>
    32           <li>On a Windows host, this file is in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installation
    33             directory, usually in <filepath>C:\Program files\Oracle\VirtualBox</filepath>. </li>
    34           <li>
    35             <p>On macOS hosts, this file is in the application bundle of <ph
    36                 conkeyref="vbox-conkeyref-phrases/product-name"/>. Right-click the <ph
    37                 conkeyref="vbox-conkeyref-phrases/product-name"/> icon in Finder and choose <b outputclass="bold">Show
    38                 Package Contents</b>. The file is located in the <filepath>Contents/MacOS</filepath> folder. </p>
    39           </li>
    40           <li>
    41             <p>On a Linux host, this file is in the <filepath>additions</filepath> folder where you installed <ph
    42                 conkeyref="vbox-conkeyref-phrases/product-name"/>, usually <filepath>/opt/VirtualBox/</filepath>. </p>
    43           </li>
    44           <li>
    45             <p>On Oracle Solaris hosts, this file is in the <filepath>additions</filepath> folder where you installed
    46                 <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, usually <filepath>/opt/VirtualBox</filepath>. </p>
    47           </li>
    48         </ul>
    49       </li>
    50       <li>
    51         <p>In the Virtual Media Manager, select the ISO file and click the <b outputclass="bold">Add</b> button. This
    52           mounts the ISO file and presents it to your Windows guest as a CD-ROM. </p>
    53       </li>
    54     </ol>
    55     <p>Unless you have the Autostart feature disabled in your Windows guest, Windows will now autostart the <ph
    56         conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions installation program from the Additions ISO.
    57       If the Autostart feature has been turned off, choose <filepath>VBoxWindowsAdditions.exe</filepath> from the CD/DVD
    58       drive inside the guest to start the installer. </p>
    59     <p>The installer will add several device drivers to the Windows driver database and then invoke the hardware
    60       detection wizard. </p>
    61     <p>Depending on your configuration, it might display warnings that the drivers are not digitally signed. You must
    62       confirm these in order to continue the installation and properly install the Additions. </p>
    63     <p>After installation, reboot your guest operating system to activate the Additions. </p>
     12    <p>For completely unattended guest installations, you can specify a command line parameter to the install launcher: </p>
     13    <pre xml:space="preserve">VBoxWindowsAdditions.exe /S</pre>
     14    <p>This automatically installs the right files and drivers for the corresponding platform, either 32-bit or 64-bit.</p>
     15    <note>
     16      <p>For Windows Aero to run correctly on a guest, the guest's VRAM size needs to be configured to at least 128 MB.</p>
     17    </note>
     18    <p>For more options regarding unattended guest installations, consult the command line help by using the command:</p>
     19    <pre xml:space="preserve">VBoxWindowsAdditions.exe /?</pre>
    6420  </body>
    6521 

  • trunk/doc/manual/en_US/dita/topics/settings-screen.dita

    r108297 r108796  
    77    <ul>
    88      <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>
     9        <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>
     10        <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>
    1411      </li>
    1512      <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>
     13        <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>
     14        <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>
     15        <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>
    2016        <p>See also <xref href="known-issues.dita"/>.</p>
    2117      </li>
    2218      <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>
     19        <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>
     20        <p>You can set a default scale factor for all VMs. Use the <b outputclass="bold">Display</b> tab in the Preferences window.</p>
    3121      </li>
    3222      <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>
     23        <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>
    3924        <ul>
    4025          <li>
    … …  
    4328                later.
    4429              </p>
    45             <p>This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option. </p>
     30            <p>This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option.</p>
    4631          </li>
    4732          <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>
     33            <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>
    5334            <p>3D acceleration is not supported for this graphics controller. </p>
    5435          </li>
    5536          <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>
     37            <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>
    6138          </li>
    6239          <li>
    63             <p><b outputclass="bold">None:</b> Does not emulate
    64                 a graphics adapter type.
    65               </p>
     40            <p><b outputclass="bold">None:</b> Does not emulate a graphics adapter type.</p>
    6641          </li>
    6742        </ul>
    6843      </li>
    6944      <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>
     45        <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. With 3D acceleration enabled, the VM also uses video decoding acceleration if the host also supports video decoding acceleration. See <xref href="guestadd-video.dita"/>.</p>
    7246      </li>
    7347    </ul>

  • trunk/doc/manual/en_US/dita/topics/sysprep.dita

    r107390 r108796  
    55 
    66  <body>
    7     <p>Microsoft offers a system preparation tool called Sysprep, to prepare a Windows system for deployment or
    8       redistribution. Some Windows releases include Sysprep on the installation medium, but the tool is also available
    9       for download from the Microsoft website. In a standard For most Windows versions, Sysprep is included in a default
    10       installation. Sysprep mainly consists of an executable called <userinput>sysprep.exe</userinput> which is invoked
    11       by the user to put the Windows installation into preparation mode. </p>
     7    <p>Microsoft offers a system preparation tool called Sysprep, to prepare a Windows system for deployment or redistribution. For most Windows versions, Sysprep is included in a default installation. Sysprep mainly consists of an executable called <userinput>sysprep.exe</userinput> which is invoked by the user to put the Windows installation into preparation mode. </p>
    128    <p>The Guest Additions offer a way to launch a system preparation on the guest operating system in an automated way,
    139      controlled from the host system. See <xref href="guestadd-guestcontrol.dita">Guest Control of Applications</xref>
    … …  
    1612      credentials. Sysprep is then started with the required system rights. </p>
    1713    <note>
    18       <p>Specifying the location of <userinput>sysprep.exe</userinput> is <b outputclass="bold">not possible</b>.
    19         Instead the following paths are used, based on the Windows release: </p>
     14      <p>Specifying the location of <userinput>sysprep.exe</userinput> is <b outputclass="bold">not possible</b>. Instead the following paths are used, based on the Windows release:</p>
    2015      <ul>
    2116        <li>
    22           <p><filepath>C:\sysprep\sysprep.exe</filepath> for Windows XP
    23               and earlier
    24             </p>
     17          <p><filepath>C:\sysprep\sysprep.exe</filepath> for Windows XP and earlier</p>
    2518        </li>
    2619        <li>
    27           <p><filepath>%WINDIR%\System32\sysprep\sysprep.exe</filepath>
    28               for Windows Vista and later
    29             </p>
     20          <p><filepath>%WINDIR%\System32\sysprep\sysprep.exe</filepath> for Windows Vista and later</p>
    3021        </li>
    3122      </ul>
    32       <p>The Guest Additions will automatically use the appropriate path to execute the system preparation tool. </p>
     23      <p>The Guest Additions will automatically use the appropriate path to execute the system preparation tool.</p>
    3324    </note>
    3425  </body>

  • trunk/doc/manual/en_US/dita/topics/windows-guest-file-extraction.dita

    r107390 r108796  
    66                 
    77                  <body>
    8                      <p>If you would like to install the files and drivers manually, you can extract the files from the
    9       Windows Guest Additions setup as follows: </p>
     8                     <p>If you would like to install the files and drivers manually, you can extract the files from the Windows Guest Additions setup as follows:</p>
    109                     <pre xml:space="preserve">VBoxWindowsAdditions.exe /extract</pre>
    11                      <p>To explicitly extract the Windows Guest Additions for another platform than the current running
    12       one, such as 64-bit files on a 32-bit system, you must use the appropriate platform installer. Use
    13         <filepath>VBoxWindowsAdditions-x86.exe</filepath> or <filepath>VBoxWindowsAdditions-amd64.exe</filepath> with
    14       the <codeph>/extract</codeph> parameter. </p>
     10                     <p>To explicitly extract the Windows Guest Additions for another platform than the current running one, such as 64-bit files on a 32-bit system, you must use the appropriate platform installer. Use <filepath>VBoxWindowsAdditions-x86.exe</filepath> or <filepath>VBoxWindowsAdditions-amd64.exe</filepath> with the <codeph>/extract</codeph> parameter.</p>
    1511                  </body>
    1612                 
Note: See TracChangeset for help on using the changeset viewer.

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