|
Last change
on this file since 108796 was 108796, checked in by vboxsync, 7 weeks ago |
|
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
|
-
Property svn:eol-style
set to
native
-
Property svn:keywords
set to
Author Date Id Revision
|
|
File size:
2.4 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="vboxdrmclient">
|
|---|
| 4 | <title>Using VBoxDRMClient to Manage Linux Guest Properties</title>
|
|---|
| 5 | <body>
|
|---|
| 6 | <p>Linux guest screen resize functionality for guests running VMSVGA graphics configuration uses a standalone daemon called <cmdname>VBoxDRMClient</cmdname> and its Desktop Environment helper counterpart.</p>
|
|---|
| 7 | <p><cmdname>VBoxDRMClient</cmdname> runs as a root process and is a bridge between the host and the guest's <cmdname>vmwgfx</cmdname> driver. This means that <cmdname>VBoxDRMClient</cmdname> listens to screen resize hints from the host and forwards them to the <cmdname>vmwgfx</cmdname> driver. This enables guest screen resize functionality to be available before the user has logged in using a GUI.</p>
|
|---|
| 8 | <p>In order to perform Desktop Environment specific actions, such as setting the primary screen in a multimonitor setup, a Desktop Environment helper is used. Once the user has performed a graphical login operation, the helper daemon starts with user session scope and attempts to connect to <cmdname>VBoxDRMClient</cmdname> using an IPC connection. When <cmdname>VBoxDRMClient</cmdname> has received a corresponding command from the host, it is forwarded to the helper daemon over IPC and the action is then performed.</p>
|
|---|
| 9 | <p>By default, <cmdname>VBoxDRMClient</cmdname> allows any process to connect to its IPC socket. This can be restricted by using the following steps:</p>
|
|---|
| 10 | <ol>
|
|---|
| 11 | <li>
|
|---|
| 12 | <p>The Guest Additions Linux installer creates a <codeph>vboxdrmipc</codeph> user group. A corresponding user needs to be added to this group.</p>
|
|---|
| 13 | </li>
|
|---|
| 14 | <li>
|
|---|
| 15 | <p>You must set the <codeph>DRMIpcRestricted</codeph> guest property, as follows:</p>
|
|---|
| 16 | <pre xml:space="preserve">VBoxManage guestproperty set "VM name" /VirtualBox/GuestAdd/DRMIpcRestricted 1 \
|
|---|
| 17 | --flags RDONLYGUEST</pre>
|
|---|
| 18 | <p>It is important to set only the <codeph>RDONLYGUEST</codeph> flag for the property, so that it cannot be changed from inside the guest.</p>
|
|---|
| 19 | </li>
|
|---|
| 20 | </ol>
|
|---|
| 21 | <note>
|
|---|
| 22 | <p>Both steps are required. If one of them is missing, all processes will have access to the IPC socket.</p>
|
|---|
| 23 | </note>
|
|---|
| 24 | <p>Restricted mode can be disabled by unsetting the guest property, as follows:</p>
|
|---|
| 25 | <pre xml:space="preserve">VBoxManage guestproperty unset "VM name" /VirtualBox/GuestAdd/DRMIpcRestricted</pre>
|
|---|
| 26 | </body>
|
|---|
| 27 | </topic>
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
