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>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>
|
---|
54 | </body>
|
---|
55 |
|
---|
56 | </topic>
|
---|