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