Changeset 42419 in vbox
- Timestamp:
- Jul 26, 2012 5:12:47 PM (12 years ago)
- File:
-
- 1 edited
-
trunk/doc/manual/en_US/user_AdvancedTopics.xml (modified) (9 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_AdvancedTopics.xml
r42329 r42419 1544 1544 1545 1545 <sect2 id="disabletimesync"> 1546 1546 1547 1547 <title>Disabling the Guest Additions time synchronization</title> 1548 1548 … … 1728 1728 <sect2> 1729 1729 <title>GUI customization</title> 1730 1730 1731 1731 <para>There are several advanced customization settings for locking down 1732 1732 the VirtualBox manager, that is, removing some features that the user … … 1866 1866 <screen>VBoxManage setextradata global GUI/Input/MachineShortcuts "FullscreenMode=None,SeamlessMode=None"</screen> 1867 1867 </para> 1868 1868 1869 1869 </sect2> 1870 1870 <sect2> 1871 1871 <title>Action when terminating the VM</title> 1872 1872 1873 1873 <para>You can disallow certain actions when terminating a VM. To disallow specific actions, type:</para> 1874 1874 … … 2095 2095 <para>Starting with VirtualBox 4.2 the memory ballooning service formerly 2096 2096 known as <computeroutput>VBoxBalloonCtrl</computeroutput> was renamed to 2097 VBoxWatchdog, which now incorporates several host services that are meant 2097 VBoxWatchdog, which now incorporates several host services that are meant 2098 2098 to be run in a server environment.</para> 2099 2099 2100 2100 <para>These services are: <itemizedlist> 2101 2101 <listitem> 2102 <para>Memory ballooning control, which automatically takes care of 2102 <para>Memory ballooning control, which automatically takes care of 2103 2103 a VM's configured memory balloon (see <xref linkend="guestadd-balloon" /> 2104 for an introduction to memory ballooning). This especially is useful 2105 for server environments where VMs may dynamically require more or 2104 for an introduction to memory ballooning). This especially is useful 2105 for server environments where VMs may dynamically require more or 2106 2106 less memory during runtime.</para> 2107 2107 … … 2114 2114 <para>Host isolation detection, which provides a way to detect whether 2115 2115 the host cannot reach the specific VirtualBox server instance anymore 2116 and take appropriate actions, such as shutting down, saving the 2116 and take appropriate actions, such as shutting down, saving the 2117 2117 current state or even powering down certain VMs.</para> 2118 2118 </listitem> 2119 2119 </itemizedlist></para> 2120 2120 2121 2121 <para> 2122 2122 All configuration values can be either specified via command line or global 2123 2123 extradata, whereas command line values always have a higher priority when set. 2124 2124 Some of the configuration values also be be specified on a per-VM basis. So 2125 the overall lookup order is: command line, per-VM basis extradata (if available), 2125 the overall lookup order is: command line, per-VM basis extradata (if available), 2126 2126 global extradata. 2127 2127 </para> 2128 2128 2129 2129 <sect2 id="vboxwatchdog-ballonctrl"> 2130 2130 <title>Memory ballooning control</title> 2131 2131 <para>The memory ballooning control inflates and deflates the memory balloon 2132 2132 of VMs based on the VMs free memory and the desired maximum balloon size.</para> 2133 2133 2134 2134 <para>To set up the memory ballooning control the maximum ballooning size a 2135 VM can reach needs to be set. This can be specified via command line with 2136 <screen>--balloon-max <Size in MB></screen>, on a per-VM basis extradata value with 2135 VM can reach needs to be set. This can be specified via command line with 2136 <screen>--balloon-max <Size in MB></screen>, on a per-VM basis extradata value with 2137 2137 <screen>VBoxManage setextradata <VM-Name> VBoxInternal2/Watchdog/BalloonCtrl/BalloonSizeMax <Size in MB></screen> 2138 2138 or using a global extradata value with … … 2141 2141 the parameters above, no ballooning will be performed at all.</para></note> 2142 2142 </para> 2143 2144 <para>Setting the ballooning increment in MB can be either done via 2143 2144 <para>Setting the ballooning increment in MB can be either done via 2145 2145 command line with 2146 <screen>--balloon-inc <Size in MB></screen> or using a global 2146 <screen>--balloon-inc <Size in MB></screen> or using a global 2147 2147 extradata value with 2148 2148 <screen>VBoxManage setextradata global VBoxInternal2/Watchdog/BalloonCtrl/BalloonIncrementMB <Size in MB></screen> 2149 2149 Default ballooning increment is 256 MB if not specified.</para> 2150 2150 2151 2151 <para>Same goes with the ballooning decrement: Via command line with 2152 <screen>--balloon-dec <Size in MB></screen> or using a global 2152 <screen>--balloon-dec <Size in MB></screen> or using a global 2153 2153 extradata value with 2154 2154 <screen>VBoxManage setextradata global VBoxInternal2/Watchdog/BalloonCtrl/BalloonDecrementMB <Size in MB></screen> 2155 2155 Default ballooning decrement is 128 MB if not specified.</para> 2156 2156 2157 2157 <para>To define the lower limit in MB a balloon can be the command line with 2158 <screen>--balloon-lower-limit <Size in MB></screen> can be used or using a global 2158 <screen>--balloon-lower-limit <Size in MB></screen> can be used or using a global 2159 2159 extradata value with 2160 2160 <screen>VBoxManage setextradata global VBoxInternal2/Watchdog/BalloonCtrl/BalloonLowerLimitMB <Size in MB></screen> 2161 2161 is available. Default lower limit is 128 if not specified.</para> 2162 2162 </sect2> 2163 2163 2164 2164 <sect2 id="vboxwatchdog-hostisln"> 2165 2165 <title>Host isolation detection</title> … … 2168 2168 alternating value to a global extradata value within a time period. If 2169 2169 this value is not set within that time period a timeout occurred and the 2170 so-called host isolation response will be performed to the VMs handled. 2170 so-called host isolation response will be performed to the VMs handled. 2171 2171 Which VMs are handled can be controlled by defining VM groups and assigning 2172 2172 VMs to those groups. By default no groups are set, meaning that all VMs 2173 on the server will be handled when no host response is received within 2173 on the server will be handled when no host response is received within 2174 2174 30 seconds.</para> 2175 2175 2176 2176 <para>To set the groups handled by the host isolation detection via 2177 2177 command line: 2178 <screen>--apimon-groups=<string[,stringN]></screen> or using a global 2178 <screen>--apimon-groups=<string[,stringN]></screen> or using a global 2179 2179 extradata value with 2180 2180 <screen>VBoxManage setextradata global VBoxInternal2/Watchdog/APIMonitor/Groups <string[,stringN]></screen> 2181 2181 </para> 2182 2182 2183 2183 <para>To set the host isolation timeout via command line: 2184 <screen>--apimon-isln-timeout=<ms></screen> or using a global 2184 <screen>--apimon-isln-timeout=<ms></screen> or using a global 2185 2185 extradata value with 2186 2186 <screen>VBoxManage setextradata global VBoxInternal2/Watchdog/APIMonitor/IsolationTimeoutMS <ms></screen> 2187 2187 </para> 2188 2188 2189 2189 <para>To set the actual host isolation response via command line: 2190 <screen>--apimon-isln-response=<cmd></screen> or using a global 2190 <screen>--apimon-isln-response=<cmd></screen> or using a global 2191 2191 extradata value with 2192 2192 <screen>VBoxManage setextradata global VBoxInternal2/Watchdog/APIMonitor/IsolationResponse <cmd></screen> … … 2219 2219 </para> 2220 2220 </sect2> 2221 2221 2222 2222 <sect2 id="vboxwatchdog-moreinfo"> 2223 2223 <title>More information</title> 2224 <para>For more advanced options and parameters like verbose logging check 2225 the built-in command line help accessible with 2224 <para>For more advanced options and parameters like verbose logging check 2225 the built-in command line help accessible with 2226 2226 <computeroutput>--help</computeroutput>.</para> 2227 </sect2> 2228 2227 </sect2> 2228 2229 2229 </sect1> 2230 2230 … … 2267 2267 installed):<screen>VBoxManage setproperty vrdeextpack "Oracle VM VirtualBox Extension Pack"</screen></para> 2268 2268 </sect1> 2269 2270 <sect1 id="autostart"> 2271 <title>Starting virtual machines during system boot</title> 2272 2273 <para>Starting with VirtualBox 4.2.0 it is possible to start VMs automatically during 2274 system boot on Linux and Mac OS X for all users. </para> 2275 2276 <sect2 id="autostart-linux"> 2277 <title>Linux: starting the autostart service via <computeroutput>init</computeroutput></title> 2278 2279 <para>On Linux, the autostart service is activated by setting two variables in 2280 <computeroutput>/etc/default/virtualbox</computeroutput>. 2281 The first one is <computeroutput>VBOXAUTOSTART_DB</computeroutput> which 2282 contains an absolute path to the autostart database directory. 2283 The directory should have write access for every user who should be able to 2284 start virtual machines automatically. Furthermore the directory should have the 2285 sticky bit set. 2286 The second variable is <computeroutput>VBOXAUTOSTART_CONFIG</computeroutput> 2287 which points the service to the autostart configuration file which is used 2288 during boot to determine whether to allow individual users to start a VM 2289 automatically and configure startup delays. 2290 The config file can be placed in <computeroutput>/etc/vbox</computeroutput> 2291 and contains several options. One is <computeroutput>default_policy</computeroutput> 2292 which controls whether the autostart service allows or denies to start a VM 2293 for users which are not in the exception list. 2294 The exception list starts with <computeroutput>exception_list</computeroutput> 2295 and contains a comma seperated list with usernames. Furthermore a separate 2296 startup delay can be configured for every user to avoid overloading the host. 2297 A sample configuration is given below:</para> 2298 2299 <para><screen> 2300 # Default policy is to deny starting a VM, the other option is "allow". 2301 default_policy = deny 2302 # Users which are allowed are given below. 2303 # If the default policy is to allow starting a VM is not allowed for the users below. 2304 exception_list = bob, alice, joe 2305 2306 bob = 30 # Bobs machines will be started 30 seconds after the autostart service started 2307 alice = 180 # Alice machines will be started 180 seconds after the autostart service started 2308 joe = 240 # Joes machines will be started 240 seconds after the autostart service started 2309 </screen></para> 2310 2311 <para>Every user who wants to enable autostart for individual machines 2312 has to set the path to the autostart database directory with 2313 <screen>VBoxManage setproperty autostartdbpath <Autostart directory></screen> 2314 </para> 2315 </sect2> 2316 2317 <sect2 id="autostart-osx"> 2318 <title>Mac OS X: starting the autostart service via launchd</title> 2319 2320 <para>On Mac OS X, launchd is used to start the VirtualBox autostart service. An 2321 example configuration file can be found in 2322 <computeroutput>/Applications/VirtualBox.app/Contents/MacOS/org.virtualbox.vboxautostart.plist</computeroutput>. 2323 To enable the service copy the file to <computeroutput>/Library/LaunchDaemons</computeroutput> and change the 2324 <computeroutput>Disabled</computeroutput> key from 2325 <computeroutput>true</computeroutput> to 2326 <computeroutput>false</computeroutput>. Furthermore replace the second parameter 2327 to an existing configuration file which has the same format as on Linux (see <xref linkend="autostart-linux" />). 2328 To manually start the service use the following command: 2329 <screen>launchctl load /Library/LaunchDaemons/org.virtualbox.vboxautostart.plist</screen> 2330 For additional information on how launchd services could be 2331 configured see <literal><ulink 2332 url="http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/BPSystemStartup.html">http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/BPSystemStartup.html</ulink></literal>.</para> 2333 </sect2> 2334 </sect1> 2269 2335 </chapter>
Note:
See TracChangeset
for help on using the changeset viewer.
