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="frontends">
|
---|
4 | <title>Alternative Front Ends</title>
|
---|
5 | <body>
|
---|
6 | <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> has a very flexible internal design that enables you to use
|
---|
7 | multiple interfaces to control the same virtual machines. For example, you can start a virtual machine with the
|
---|
8 | <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window and then stop it from the command line. With <ph
|
---|
9 | conkeyref="vbox-conkeyref-phrases/product-name"/>'s support for the Remote Desktop Protocol (RDP), you can even
|
---|
10 | run virtual machines remotely on a headless server and have all the graphical output redirected over the network. </p>
|
---|
11 | <p>The following front ends are shipped in the standard <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
|
---|
12 | package:</p>
|
---|
13 | <ul>
|
---|
14 | <li>
|
---|
15 | <p><b outputclass="bold">VirtualBox.</b> This is the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, a
|
---|
16 | graphical user interface that uses the Qt toolkit. This interface is described throughout this user guide.
|
---|
17 | While this is the simplest and easiest front end to use, some of the more advanced <ph
|
---|
18 | conkeyref="vbox-conkeyref-phrases/product-name"/> features are not included.</p>
|
---|
19 | </li>
|
---|
20 | <li>
|
---|
21 | <p><b outputclass="bold">VBoxManage.</b> A command-line interface for automated and detailed control of every
|
---|
22 | aspect of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See <xref href="vboxmanage.dita#vboxmanage"
|
---|
23 | />. </p>
|
---|
24 | </li>
|
---|
25 | <li>
|
---|
26 | <p><b outputclass="bold">VBoxHeadless.</b> A front end that produces no visible output on
|
---|
27 | the host at all, but can act as a RDP server if the VirtualBox Remote Desktop Extension
|
---|
28 | (VRDE) is installed and enabled for the VM. As opposed to the other graphical interfaces,
|
---|
29 | the headless front end requires no graphics support. This is useful, for example, if you
|
---|
30 | want to host your virtual machines on a headless Linux server that has no X Window system
|
---|
31 | installed. See <xref href="vboxheadless.dita">VBoxHeadless, the Remote Desktop
|
---|
32 | Server</xref>. </p>
|
---|
33 | </li>
|
---|
34 | <li>
|
---|
35 | <p><b>Separate mode.</b> A front end that is based on <userinput>VBoxHeadless</userinput>,
|
---|
36 | but does not require VRDE or an RDP viewer. See <xref href="vboxheadless-separate-mode.dita">Separate Mode</xref>.</p>
|
---|
37 | </li>
|
---|
38 | </ul>
|
---|
39 | <p>If the above front ends still do not satisfy your particular needs, it is possible to create yet another front
|
---|
40 | end to the complex virtualization engine that is the core of <ph conkeyref="vbox-conkeyref-phrases/product-name"
|
---|
41 | />, as the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> core neatly exposes all of its features in a
|
---|
42 | clean API. See <xref href="VirtualBoxAPI.dita"><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Programming
|
---|
43 | Interfaces</xref>. </p>
|
---|
44 | </body>
|
---|
45 |
|
---|
46 | </topic>
|
---|