Changeset 42506 in vbox for trunk/doc/manual/en_US
- Timestamp:
- Aug 1, 2012 12:37:11 PM (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_Frontends.xml
r40461 r42506 186 186 follows:<screen>VBoxHeadless --startvm <uuid|name></screen></para> 187 187 188 <para>This way of starting the VM is preferred because you can see 189 more detailed error messages, especially for early failures before 190 the VM execution is started. If you have trouble with 191 <computeroutput>VBoxManage startvm</computeroutput>, it can help 192 greatly to start <computeroutput>VBoxHeadless</computeroutput> 193 directly to diagnose the problem cause.</para> 188 <para>This way of starting the VM helps troubleshooting problems 189 reported by <computeroutput>VBoxManage startvm ...</computeroutput> 190 because you can see sometimes more detailed error messages, 191 especially for early failures before the VM execution is started. 192 In normal situations <computeroutput>VBoxManage startvm</computeroutput> 193 is preferred since it runs the VM directly as a background process 194 which has to be done explicitly when directly starting 195 <computeroutput>VBoxHeadless</computeroutput>.</para> 194 196 </listitem> 195 197 </itemizedlist> … … 205 207 have the VRDP server enabled depending on the VM configuration, as the 206 208 other front-ends would, use this:<screen>VBoxHeadless --startvm <uuid|name> --vrde=config</screen></para> 209 210 <para>If you start the VM with <computeroutput>VBoxManage startvm ...</computerputput> 211 then the configuration settings of the VM are always used.</para> 207 212 </sect2> 208 213
Note:
See TracChangeset
for help on using the changeset viewer.