| 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="additions-linux-graphics-mouse">
|
|---|
| 4 | <title>Graphics and Mouse Integration</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | In Linux and Oracle Solaris guests, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphics
|
|---|
| 9 | and mouse integration goes through the X Window System.
|
|---|
| 10 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can use the X.Org variant of the system, or
|
|---|
| 11 | XFree86 version 4.3 which is identical to the first X.Org
|
|---|
| 12 | release. During the installation process, the X.Org display
|
|---|
| 13 | server will be set up to use the graphics and mouse drivers
|
|---|
| 14 | which come with the Guest Additions.
|
|---|
| 15 | </p>
|
|---|
| 16 | <p>
|
|---|
| 17 | After installing the Guest Additions into a fresh installation
|
|---|
| 18 | of a supported Linux distribution or Oracle Solaris system,
|
|---|
| 19 | many unsupported systems will work correctly too, the guest's
|
|---|
| 20 | graphics mode will change to fit the size of the
|
|---|
| 21 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> window on the host when it is resized. You can
|
|---|
| 22 | also ask the guest system to switch to a particular resolution
|
|---|
| 23 | by sending a video mode hint using the
|
|---|
| 24 | <userinput>VBoxManage</userinput> tool.
|
|---|
| 25 | </p>
|
|---|
| 26 | <p>
|
|---|
| 27 | Multiple guest monitors are supported in guests using the
|
|---|
| 28 | X.Org server version 1.3, which is part of release 7.3 of the
|
|---|
| 29 | X Window System version 11, or a later version. The layout of
|
|---|
| 30 | the guest screens can be adjusted as needed using the tools
|
|---|
| 31 | which come with the guest operating system.
|
|---|
| 32 | </p>
|
|---|
| 33 | <p>
|
|---|
| 34 | If you want to understand more about the details of how the
|
|---|
| 35 | X.Org drivers are set up, in particular if you wish to use
|
|---|
| 36 | them in a setting which our installer does not handle
|
|---|
| 37 | correctly, see <xref href="guestxorgsetup.dita">Guest Graphics and Mouse Driver Setup in Depth</xref>.
|
|---|
| 38 | </p>
|
|---|
| 39 | <p>
|
|---|
| 40 | Starting from <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7, Linux guest screen resize
|
|---|
| 41 | functionality for guests running VMSVGA graphics configuration
|
|---|
| 42 | has been changed. Since then, this functionality consists of a
|
|---|
| 43 | standalone daemon called VBoxDRMClient and its Desktop
|
|---|
| 44 | Environment helper counterpart.
|
|---|
| 45 | </p>
|
|---|
| 46 | <p>
|
|---|
| 47 | VBoxDRMClient runs as a root process and is a bridge between
|
|---|
| 48 | the host and the guest's vmwgfx driver. This means that
|
|---|
| 49 | VBoxDRMClient listens to screen resize hints from the host and
|
|---|
| 50 | forwards them to the vmwgfx driver. This enables guest screen
|
|---|
| 51 | resize functionality to be available before the user has
|
|---|
| 52 | performed a graphical login.
|
|---|
| 53 | </p>
|
|---|
| 54 | <p>
|
|---|
| 55 | In order to perform Desktop Environment specific actions, such
|
|---|
| 56 | as setting the primary screen in a multimonitor setup, a
|
|---|
| 57 | Desktop Environment helper is used. Once the user has
|
|---|
| 58 | performed a graphical login operation, the helper daemon
|
|---|
| 59 | starts with user session scope and attempts to connect to
|
|---|
| 60 | VBoxDRMClient using an IPC connection. When VBoxDRMClient has
|
|---|
| 61 | received a corresponding command from the host, it is
|
|---|
| 62 | forwarded to the helper daemon over IPC and the action is then
|
|---|
| 63 | performed.
|
|---|
| 64 | </p>
|
|---|
| 65 | <p>
|
|---|
| 66 | By default, VBoxDRMClient allows any process to connect to its
|
|---|
| 67 | IPC socket. This can be restricted by using the following
|
|---|
| 68 | steps:
|
|---|
| 69 | </p>
|
|---|
| 70 | <ol>
|
|---|
| 71 | <li>
|
|---|
| 72 | <p>
|
|---|
| 73 | The Guest Additions Linux installer creates a
|
|---|
| 74 | <codeph>vboxdrmipc</codeph> user group. A corresponding
|
|---|
| 75 | user needs to be added to this group.
|
|---|
| 76 | </p>
|
|---|
| 77 | </li>
|
|---|
| 78 | <li>
|
|---|
| 79 | <p>
|
|---|
| 80 | You must set the <codeph>DRMIpcRestricted</codeph> guest
|
|---|
| 81 | property, as follows:
|
|---|
| 82 | </p>
|
|---|
| 83 | <pre xml:space="preserve">VBoxManage guestproperty set "VM name" /VirtualBox/GuestAdd/DRMIpcRestricted 1 \
|
|---|
| 84 | --flags RDONLYGUEST</pre>
|
|---|
| 85 | <p>
|
|---|
| 86 | It is important to set only the RDONLYGUEST flag for the
|
|---|
| 87 | property, so that it cannot be changed from inside the
|
|---|
| 88 | guest.
|
|---|
| 89 | </p>
|
|---|
| 90 | </li>
|
|---|
| 91 | </ol>
|
|---|
| 92 | <note>
|
|---|
| 93 | <p>
|
|---|
| 94 | Both steps are required. If one of them is missing, all
|
|---|
| 95 | processes will have access to the IPC socket.
|
|---|
| 96 | </p>
|
|---|
| 97 | </note>
|
|---|
| 98 | <p>
|
|---|
| 99 | Restricted mode can be disabled by unsetting the guest
|
|---|
| 100 | property, as follows:
|
|---|
| 101 | </p>
|
|---|
| 102 | <pre xml:space="preserve">VBoxManage guestproperty unset "VM name" /VirtualBox/GuestAdd/DRMIpcRestricted</pre>
|
|---|
| 103 | </body>
|
|---|
| 104 |
|
|---|
| 105 | </topic>
|
|---|
