VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/headless-mode.dita@ 107390

最後變更 在這個檔案從107390是 107390,由 vboxsync 提交於 3 月 前

Docs: bugref:10705. bugref: 10829. The docs build has been modified to split generated refentry dita files and the user manual files and the following commits from doc's team git repo has been applied:

0946136c74dda0483704db891345cb39548b4e28 Started consolidating known issues and troubleshooting information
845b847e6a8e778b38a57867e25ee5e086a73800 Added individual topics for list of known issues, integrated into Troubleshooting section.
bb574836aac775889bd61e4a72f489617fcb7d18 Removed EFI firmware from experimental features for 7.2
6d2e68b244869991e713d170ecd239739d99ba56 Moved known issues into Known Issues section
e2630c896561587718b5c3197c384a38d07014d5 Merge branch 'VBP-1461_experimental-features' into 'main'
0512e2cce51f49ccdc56f3381a2a0c924f2bd278 Feedback on known issues
a77d6c980f6ff5cad9d32b2fb9290990093a03fa Restructured host and guest OS topics
988af5cc9628f5de0806531bc98686f691a911fd Updates with feedbback from Jacob
982a61c9f25b22b745ec483e763e3d88efe59c40 Included feedback from Jacob
93181c8c6cc2d9a26bcccb1145cb0423c0d9f4c9 Updated known issues with feedback from Klaus
8bc369561c383f09b409fe5e44f507440b3735fb Created Legacy Guest OS section
d7932f55accdab7a03666302d58b8c941cd48be2 Moved known issues to more appropriate places for the info
2a4aa094ba8a7ac6894d2a777316eabf41746580 Further moving of known issues
baeabd5308c5519a4dc26b4197be9b00e419a85a Updated links to cli_topics

  • 屬性 svn:eol-style 設為 native
  • 屬性 svn:keywords 設為 Author Date Id Revision
檔案大小: 4.3 KB
 
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="headless-mode">
4 <title>VBoxHeadless, the Remote Desktop Server</title>
5 <body>
6 <p>While any VM started from <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> is capable of running virtual machines remotely, it is not convenient to have to run the full GUI if you never want to have VMs displayed locally in the first place. In particular, if you are running server hardware whose only purpose is to host VMs, and all your VMs are supposed to run remotely over VRDP, then it is pointless to have a graphical user interface on the server at all. This is especially true for Linux or Oracle Solaris hosts, as the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> comes with dependencies on the Qt and SDL libraries. This is inconvenient if you would rather not have the X Window system on your server at all. </p>
7 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> therefore comes with a front end called <userinput>VBoxHeadless</userinput>, which produces no visible output on the host at all, but still can optionally deliver VRDP data. This front end has no dependencies on the X Window system on Linux and Oracle Solaris hosts. </p>
8 <note>
9 <p>In legacy releases of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, the headless server was called <userinput>VBoxVRDP</userinput>. For backward compatibility, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installation still includes an executable with that name. </p>
10 </note>
11 <p>To start a virtual machine with <userinput>VBoxHeadless</userinput>, you have the following options: </p>
12 <ul>
13 <li>
14 <p>Use the <userinput>VBoxManage</userinput> command, as follows: </p>
15 <pre xml:space="preserve">$ VBoxManage startvm <varname>VM-name</varname> --type headless</pre>
16 <p>The <codeph>--type</codeph> option causes <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to use <userinput>VBoxHeadless</userinput> as the front end to the internal virtualization engine, instead of the Qt front end. </p>
17 </li>
18 <li>
19 <p>Use the <userinput>VBoxHeadless</userinput> command, as follows: </p>
20 <pre xml:space="preserve">VBoxHeadless --startvm <varname>uuid</varname>|<varname>vmname</varname>
21 </pre>
22 <p>This way of starting the VM helps troubleshooting problems reported by <userinput>VBoxManage startvm</userinput>, because you can sometimes see more detailed error messages, especially for early failures before the VM execution is started. In normal situations <userinput>VBoxManage startvm</userinput> is preferred, since it runs the VM directly as a background process which has to be done explicitly when directly starting with <userinput>VBoxHeadless</userinput>. </p>
23 </li>
24 <li>
25 <p>Start <userinput>VBoxHeadless</userinput> from <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, by pressing the Shift key when starting a virtual machine or by selecting <b outputclass="bold">Headless Start</b> from the <b outputclass="bold">Machine</b> menu. </p>
26 </li>
27 </ul>
28 <p>When you use the <userinput>VBoxHeadless</userinput> command to start a VM, the VRDP server will be enabled according to the VM configuration. You can override the VM's setting using <codeph>--vrde</codeph> command line parameter. To enable the VRDP server, start the VM as follows: </p>
29 <pre xml:space="preserve">VBoxHeadless --startvm <varname>uuid</varname>|<varname>vmname</varname> --vrde on</pre>
30 <p>To disable the VRDP server: </p>
31 <pre xml:space="preserve">VBoxHeadless --startvm <varname>uuid</varname>|<varname>vmname</varname> --vrde off</pre>
32 <p>To have the VRDP server enabled depending on the VM configuration, as for other front ends: </p>
33 <pre xml:space="preserve">VBoxHeadless --startvm <varname>uuid</varname>|<varname>vmname</varname> --vrde config</pre>
34 <p>This command is the same as the following: </p>
35 <pre xml:space="preserve">VBoxHeadless --startvm <varname>uuid</varname>|<varname>vmname</varname>
36 </pre>
37 <p>If you start the VM with <userinput>VBoxManage startvm</userinput> then the configuration settings of the VM are always used. </p>
38 </body>
39</topic>
注意: 瀏覽 TracBrowser 來幫助您使用儲存庫瀏覽器

© 2025 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette