| 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="vboxwatchdog">
|
|---|
| 4 | <title>Oracle VM VirtualBox Watchdog</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | The memory ballooning service, formerly known as
|
|---|
| 9 | <userinput>VBoxBalloonCtrl</userinput>, was renamed to VBoxWatchdog.
|
|---|
| 10 | This service now incorporates the following host services that are
|
|---|
| 11 | meant to be run in a server environment:
|
|---|
| 12 | </p>
|
|---|
| 13 | <ul>
|
|---|
| 14 | <li>
|
|---|
| 15 | <p><b outputclass="bold">Memory ballooning control.</b>
|
|---|
| 16 | This service automatically takes care of a VM's configured
|
|---|
| 17 | memory balloon. See <xref href="guestadd-balloon.dita">Memory Ballooning</xref>. This
|
|---|
| 18 | service is useful for server environments where VMs may
|
|---|
| 19 | dynamically require more or less memory during runtime.
|
|---|
| 20 | </p>
|
|---|
| 21 | <p>
|
|---|
| 22 | The service periodically checks a VM's current memory balloon
|
|---|
| 23 | and its free guest RAM and automatically adjusts the current
|
|---|
| 24 | memory balloon by inflating or deflating it accordingly. This
|
|---|
| 25 | handling only applies to running VMs having recent Guest
|
|---|
| 26 | Additions installed.
|
|---|
| 27 | </p>
|
|---|
| 28 | </li>
|
|---|
| 29 | <li>
|
|---|
| 30 | <p><b outputclass="bold">Host isolation detection.</b>
|
|---|
| 31 | This service provides a way to detect whether the host cannot
|
|---|
| 32 | reach the specific Oracle VM VirtualBox server instance anymore and
|
|---|
| 33 | take appropriate actions, such as shutting down, saving the
|
|---|
| 34 | current state or even powering down certain VMs.
|
|---|
| 35 | </p>
|
|---|
| 36 | </li>
|
|---|
| 37 | </ul>
|
|---|
| 38 | <p>
|
|---|
| 39 | All configuration values can be either specified using the command
|
|---|
| 40 | line or global extradata, whereas command line values always have
|
|---|
| 41 | a higher priority when set. Some of the configuration values also
|
|---|
| 42 | be specified on a per-VM basis. So the overall lookup order is:
|
|---|
| 43 | command line, per-VM basis extradata if available, global
|
|---|
| 44 | extradata.
|
|---|
| 45 | </p>
|
|---|
| 46 | </body>
|
|---|
| 47 | </topic>
|
|---|
