File: vboxwatchdog-hostisln.dita

package info (click to toggle)
virtualbox 7.1.12-dfsg-2
  • links: PTS, VCS
  • area: contrib
  • in suites: sid
  • size: 565,672 kB
  • sloc: ansic: 2,330,854; cpp: 2,193,228; asm: 230,777; python: 223,895; xml: 86,771; sh: 25,541; makefile: 8,158; perl: 5,697; java: 5,337; cs: 4,872; pascal: 1,782; javascript: 1,692; objc: 1,131; lex: 931; php: 906; sed: 899; yacc: 707
file content (55 lines) | stat: -rw-r--r-- 2,931 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic xml:lang="en-us" id="vboxwatchdog-hostisln">
  <title>Host Isolation Detection</title>
  
  <body>
    <p>To detect whether a host is being isolated, that is, the host cannot reach the <ph
        conkeyref="vbox-conkeyref-phrases/product-name"/> server instance anymore, the host needs to set an alternating
      value to a global extradata value within a time period. If this value is not set within that time period a timeout
      occurred and the so-called host isolation response will be performed to the VMs handled. Which VMs are handled can
      be controlled by defining VM groups and assigning VMs to those groups. By default no groups are set, meaning that
      all VMs on the server will be handled when no host response is received within 30 seconds. </p>
    <p>Set the groups handled by the host isolation detection using the following command line: </p>
    <pre xml:space="preserve">--apimon-groups=&lt;string[,stringN]&gt;</pre>
    <p>Using a global extradata value, as follows: </p>
    <pre xml:space="preserve">VBoxManage setextradata global VBoxInternal2/Watchdog/APIMonitor/Groups &lt;string[,stringN]&gt;</pre>
    <p>Set the host isolation timeout using the following command line: </p>
    <pre xml:space="preserve">--apimon-isln-timeout=&lt;ms&gt;</pre>
    <p>Using a global extradata value, as follows: </p>
    <pre xml:space="preserve">VBoxManage setextradata global VBoxInternal2/Watchdog/APIMonitor/IsolationTimeoutMS &lt;ms&gt;</pre>
    <p>Set the actual host isolation response using the following command line: </p>
    <pre xml:space="preserve">--apimon-isln-response=&lt;cmd&gt;</pre>
    <p>Using a global extradata value, as follows: </p>
    <pre xml:space="preserve">VBoxManage setextradata global VBoxInternal2/Watchdog/APIMonitor/IsolationResponse &lt;cmd&gt;</pre>
    <p>The following response commands are available: </p>
    <ul>
      <li>
        <p><codeph>none</codeph>. This has no effect.
          </p>
      </li>
      <li>
        <p><codeph>pause</codeph>. Pauses the execution of a VM.
          </p>
      </li>
      <li>
        <p><codeph>poweroff</codeph>. Shuts down the VM by pressing
            the virtual power button. The VM will not have the chance of
            saving any data or veto the shutdown process.
          </p>
      </li>
      <li>
        <p><codeph>save</codeph>. Saves the current machine state and then powers off the VM. If
          saving the machine state fails the VM will be paused. </p>
      </li>
      <li>
        <p><codeph>shutdown</codeph>. Shuts down the VM in a gentle
            way by sending an <codeph>ACPI</codeph> shutdown event to
            the VM's operating system. The OS then has the chance of
            doing a clean shutdown.
          </p>
      </li>
    </ul>
  </body>
  
</topic>