File: startingvboxonlinux.dita

package info (click to toggle)
virtualbox 7.1.12-dfsg-2
  • links: PTS, VCS
  • area: contrib
  • in suites: sid
  • size: 565,672 kB
  • sloc: ansic: 2,330,854; cpp: 2,193,228; asm: 230,777; python: 223,895; xml: 86,771; sh: 25,541; makefile: 8,158; perl: 5,697; java: 5,337; cs: 4,872; pascal: 1,782; javascript: 1,692; objc: 1,131; lex: 931; php: 906; sed: 899; yacc: 707
file content (29 lines) | stat: -rw-r--r-- 2,356 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic
  PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic xml:lang="en-us" id="startingvboxonlinux">
               <title>Starting <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on Linux</title>
               
               <body>
                  <p>The easiest way to start an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> program is by
      running the program of your choice (<userinput>VirtualBox</userinput>, <userinput>VBoxManage</userinput>, or
        <userinput>VBoxHeadless</userinput>) from a terminal. These are symbolic links to <userinput>VBox.sh</userinput>
      that start the required program for you. </p>
                  <p>The following detailed instructions should only be of interest if you want to execute <ph
        conkeyref="vbox-conkeyref-phrases/product-name"/> without installing it first. You should start by compiling the
        <userinput>vboxdrv</userinput> kernel module and inserting it into the Linux kernel. <ph
        conkeyref="vbox-conkeyref-phrases/product-name"/> consists of a service daemon, <userinput>VBoxSVC</userinput>,
      and several application programs. The daemon is automatically started if necessary. All <ph
        conkeyref="vbox-conkeyref-phrases/product-name"/> applications will communicate with the daemon through UNIX
      local domain sockets. There can be multiple daemon instances under different user accounts and applications can
      only communicate with the daemon running under the user account as the application. The local domain socket
      resides in a subdirectory of your system's directory for temporary files called
        <filepath>.vbox-&lt;username&gt;-ipc</filepath>. In case of communication problems or server startup problems,
      you may try to remove this directory. </p>
                  <p>All <ph conkeyref="vbox-conkeyref-phrases/product-name"/> applications
        (<userinput>VirtualBox</userinput>, <userinput>VBoxManage</userinput>, and <userinput>VBoxHeadless</userinput>)
      require the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> directory to be in the library path, as follows: </p>
                  <pre xml:space="preserve">LD_LIBRARY_PATH=. ./VBoxManage showvminfo "Windows XP"</pre>
               </body>
               
            </topic>