| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="guestxorgsetup">
|
|---|
| 4 | <title>Guest Graphics and Mouse Driver Setup in Depth</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>This section assumes that you are familiar with configuring the X.Org server using xorg.conf and optionally the
|
|---|
| 8 | newer mechanisms using hal or udev and xorg.conf.d. If not you can learn about them by studying the documentation
|
|---|
| 9 | which comes with X.Org. </p>
|
|---|
| 10 | <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions includes drivers for X.Org. By default
|
|---|
| 11 | these drivers are in the following directory: </p>
|
|---|
| 12 | <p><filepath>/opt/VBoxGuestAdditions-<varname>version</varname>/other/</filepath>
|
|---|
| 13 | </p>
|
|---|
| 14 | <p>The correct versions for the X server are symbolically linked into the X.Org driver directories. </p>
|
|---|
| 15 | <p>For graphics integration to work correctly, the X server must load the <codeph>vboxvideo</codeph> driver. Many
|
|---|
| 16 | recent X server versions look for it automatically if they see that they are running in <ph
|
|---|
| 17 | conkeyref="vbox-conkeyref-phrases/product-name"/>. For an optimal user experience, the guest kernel drivers must
|
|---|
| 18 | be loaded and the Guest Additions tool <userinput>VBoxClient</userinput> must be running as a client in the X
|
|---|
| 19 | session. </p>
|
|---|
| 20 | <p>For mouse integration to work correctly, the guest kernel drivers must be loaded. In addition, for legacy X
|
|---|
| 21 | servers the correct <codeph>vboxmouse</codeph> driver must be loaded and associated with
|
|---|
| 22 | <filepath>/dev/mouse</filepath> or <filepath>/dev/psaux</filepath>. For most guests, a driver for a PS/2 mouse
|
|---|
| 23 | must be loaded and the correct vboxmouse driver must be associated with <filepath>/dev/vboxguest</filepath>. </p>
|
|---|
| 24 | <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> guest graphics driver can use any graphics
|
|---|
| 25 | configuration for which the virtual resolution fits into the virtual video memory allocated to the virtual
|
|---|
| 26 | machine, minus a small amount used by the guest driver, as described in <xref href="settings-display.dita">Display
|
|---|
| 27 | Settings</xref>. The driver will offer a range of standard modes at least up to the default guest resolution for
|
|---|
| 28 | all active guest monitors. The default mode can be changed by setting the output property VBOX_MODE to
|
|---|
| 29 | "<width>x<height>" for any guest monitor. When VBoxClient and the kernel drivers are active this is
|
|---|
| 30 | done automatically when the host requests a mode change. The driver for older versions can only receive new modes
|
|---|
| 31 | by querying the host for requests at regular intervals. </p>
|
|---|
| 32 | <p>With legacy X Servers before version 1.3, you can also add your own modes to the X server configuration file. Add
|
|---|
| 33 | them to the "Modes" list in the "Display" subsection of the "Screen" section. For example, the following section
|
|---|
| 34 | has a custom 2048x800 resolution mode added: </p>
|
|---|
| 35 | <pre xml:space="preserve">Section "Screen"
|
|---|
| 36 | Identifier "Default Screen"
|
|---|
| 37 | Device "VirtualBox graphics card"
|
|---|
| 38 | Monitor "Generic Monitor"
|
|---|
| 39 | DefaultDepth 24
|
|---|
| 40 | SubSection "Display"
|
|---|
| 41 | Depth 24
|
|---|
| 42 | Modes "2048x800" "800x600" "640x480"
|
|---|
| 43 | EndSubSection
|
|---|
| 44 | EndSection</pre>
|
|---|
| 45 | </body>
|
|---|
| 46 |
|
|---|
| 47 | </topic>
|
|---|
