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
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
|
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic xml:lang="en-us" id="vboxwatchdog-linux">
<title>Linux: Starting the Watchdog Service With init</title>
<body>
<p>On Linux, the watchdog service can be automatically started during host boot by adding appropriate parameters to
the file <filepath>/etc/default/virtualbox</filepath>. There is one mandatory parameter,
<codeph>VBOXWATCHDOG_USER</codeph>, which must be set to the user which will later start the VMs. For backward
compatibility you can also specify <codeph>VBOXBALLOONCTRL_USER</codeph>. </p>
<p>The parameters in the following table all start with the <codeph>VBOXWATCHDOG_</codeph> prefix string. For
example: <codeph>VBOXWATCHDOG_BALLOON_INTERVAL</codeph> and <codeph>VBOXWATCHDOG_LOGSIZE</codeph>. Legacy
parameters such as <codeph>VBOXBALLOONCTRL_INTERVAL</codeph> can still be used. </p>
<table id="table-vboxwatchdog-config-params">
<title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Watchdog Configuration Parameters</title>
<desc><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Watchdog Configuration Parameters</desc>
<tgroup cols="3">
<thead>
<row>
<entry>
<p>
<b outputclass="bold">Parameter</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">Description</b>
</p>
</entry>
<entry>
<p>
<b outputclass="bold">Default</b>
</p>
</entry>
</row>
</thead>
<tbody>
<row>
<entry>
<p>
<codeph>USER</codeph>
</p>
</entry>
<entry>
<p>
The user which the watchdog service runs as
</p>
</entry>
<entry>
<p/>
</entry>
</row>
<row>
<entry>
<p>
<codeph>ROTATE</codeph>
</p>
</entry>
<entry>
<p>
Number of log files, 0 disables log rotation
</p>
</entry>
<entry>
<p>
10
</p>
</entry>
</row>
<row>
<entry>
<p>
<codeph>LOGSIZE</codeph>
</p>
</entry>
<entry>
<p>
Maximum log file size to trigger rotation, in bytes
</p>
</entry>
<entry>
<p>
1MB
</p>
</entry>
</row>
<row>
<entry>
<p>
<codeph>LOGINTERVAL</codeph>
</p>
</entry>
<entry>
<p>
Maximum time interval to trigger log rotation, in
seconds
</p>
</entry>
<entry>
<p>
1 day
</p>
</entry>
</row>
<row>
<entry>
<p>
<codeph>BALLOON_INTERVAL</codeph>
</p>
</entry>
<entry>
<p>
Interval for checking the balloon size, in
milliseconds
</p>
</entry>
<entry>
<p>
30000
</p>
</entry>
</row>
<row>
<entry>
<p>
<codeph>BALLOON_INCREMENT</codeph>
</p>
</entry>
<entry>
<p>
Balloon size increment, in megabytes
</p>
</entry>
<entry>
<p>
256
</p>
</entry>
</row>
<row>
<entry>
<p>
<codeph>BALLOON_DECREMENT</codeph>
</p>
</entry>
<entry>
<p>
Balloon size decrement, in megabytes
</p>
</entry>
<entry>
<p>
128
</p>
</entry>
</row>
<row>
<entry>
<p>
<codeph>BALLOON_LOWERLIMIT</codeph>
</p>
</entry>
<entry>
<p>
Balloon size lower limit, in megabytes
</p>
</entry>
<entry>
<p>
64
</p>
</entry>
</row>
<row>
<entry>
<p>
<codeph>BALLOON_SAFETYMARGIN</codeph>
</p>
</entry>
<entry>
<p>
Free memory required for decreasing the balloon size,
in megabytes
</p>
</entry>
<entry>
<p>
1024
</p>
</entry>
</row>
</tbody>
</tgroup>
</table>
</body>
</topic>
|
