VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/guestxorgsetup.dita@ 105293

Last change on this file since 105293 was 99797, checked in by vboxsync, 21 months ago

Docs: bugref:10302. Merging changes from the docs team. Almost exclusively conkeyref related stuff.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 3.5 KB
Line 
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>
8 This section assumes that you are familiar with configuring the
9 X.Org server using xorg.conf and optionally the newer mechanisms
10 using hal or udev and xorg.conf.d. If not you can learn about
11 them by studying the documentation which comes with X.Org.
12 </p>
13 <p>
14 The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions includes drivers for X.Org.
15 By default these drivers are in the following directory:
16 </p>
17 <p>
18 <filepath>/opt/VBoxGuestAdditions-<varname>version</varname>/other/</filepath>
19 </p>
20 <p>
21 The correct versions for the X server are symbolically linked
22 into the X.Org driver directories.
23 </p>
24 <p>
25 For graphics integration to work correctly, the X server must
26 load the <codeph>vboxvideo</codeph> driver. Many recent X
27 server versions look for it automatically if they see that they
28 are running in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. For an optimal user experience,
29 the guest kernel drivers must be loaded and the Guest Additions
30 tool <userinput>VBoxClient</userinput> must be running as a client
31 in the X session.
32 </p>
33 <p>
34 For mouse integration to work correctly, the guest kernel
35 drivers must be loaded. In addition, for legacy X servers the
36 correct <codeph>vboxmouse</codeph> driver must be loaded and
37 associated with <filepath>/dev/mouse</filepath> or
38 <filepath>/dev/psaux</filepath>. For most guests, a driver for a
39 PS/2 mouse must be loaded and the correct vboxmouse driver must
40 be associated with <filepath>/dev/vboxguest</filepath>.
41 </p>
42 <p>
43 The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> guest graphics driver can use any graphics
44 configuration for which the virtual resolution fits into the
45 virtual video memory allocated to the virtual machine, minus a
46 small amount used by the guest driver, as described in
47 <xref href="settings-display.dita">Display Settings</xref>. The driver will offer a
48 range of standard modes at least up to the default guest
49 resolution for all active guest monitors. The default mode can
50 be changed by setting the output property VBOX_MODE to
51 "&lt;width&gt;x&lt;height&gt;" for any guest monitor. When
52 VBoxClient and the kernel drivers are active this is done
53 automatically when the host requests a mode change. The driver
54 for older versions can only receive new modes by querying the
55 host for requests at regular intervals.
56 </p>
57 <p>
58 With legacy X Servers before version 1.3, you can also add your
59 own modes to the X server configuration file. Add them to the
60 "Modes" list in the "Display" subsection of the "Screen"
61 section. For example, the following section has a custom
62 2048x800 resolution mode added:
63 </p>
64 <pre xml:space="preserve">Section "Screen"
65 Identifier "Default Screen"
66 Device "VirtualBox graphics card"
67 Monitor "Generic Monitor"
68 DefaultDepth 24
69 SubSection "Display"
70 Depth 24
71 Modes "2048x800" "800x600" "640x480"
72 EndSubSection
73EndSection</pre>
74 </body>
75
76</topic>
Note: See TracBrowser for help on using the repository browser.

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