| 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="ts_linux-host-vboxsvc">
|
|---|
| 4 | <title>VBoxSVC IPC Issues</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | On Linux, Oracle VM VirtualBox makes use of a custom version of
|
|---|
| 9 | Mozilla XPCOM (cross platform component object model) for
|
|---|
| 10 | interprocess and intraprocess communication (IPC). The process
|
|---|
| 11 | <userinput>VBoxSVC</userinput> serves as a communication hub between
|
|---|
| 12 | different Oracle VM VirtualBox processes and maintains the global
|
|---|
| 13 | configuration, such as the XML database. When starting an
|
|---|
| 14 | Oracle VM VirtualBox component, the processes
|
|---|
| 15 | <userinput>VBoxSVC</userinput> and <userinput>VBoxXPCOMIPCD</userinput>
|
|---|
| 16 | are started automatically. They are only accessible from the
|
|---|
| 17 | user account they are running under. <userinput>VBoxSVC</userinput>
|
|---|
| 18 | owns the Oracle VM VirtualBox configuration database which normally
|
|---|
| 19 | resides in <filepath>~/.config/VirtualBox</filepath>, or the
|
|---|
| 20 | appropriate configuration directory for your operating system.
|
|---|
| 21 | While it is running, the configuration files are locked.
|
|---|
| 22 | Communication between the various Oracle VM VirtualBox components and
|
|---|
| 23 | <userinput>VBoxSVC</userinput> is performed through a local domain
|
|---|
| 24 | socket residing in
|
|---|
| 25 | <filepath>/tmp/.vbox-<varname>username</varname>-ipc</filepath>.
|
|---|
| 26 | In case there are communication problems, such as an
|
|---|
| 27 | Oracle VM VirtualBox application cannot communicate with
|
|---|
| 28 | <userinput>VBoxSVC</userinput>, terminate the daemons and remove the
|
|---|
| 29 | local domain socket directory.
|
|---|
| 30 | </p>
|
|---|
| 31 | </body>
|
|---|
| 32 |
|
|---|
| 33 | </topic>
|
|---|
