Changeset 56466 in vbox for trunk/doc/manual/en_US
- Timestamp:
- Jun 16, 2015 11:46:25 PM (10 years ago)
- Location:
- trunk/doc/manual/en_US
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/man_VBoxManage_debugvm.xml
r56445 r56466 141 141 142 142 <refsect2 id="vboxmanage-debugvm-dumpvmcore"> 143 <cmdsynopsis> 144 <command>VBoxManage debugvm</command> 145 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 146 <arg choice="plain">dumpvmcore</arg> 147 <arg>--filename <replaceable>name</replaceable></arg> 148 </cmdsynopsis> 143 <title>VBoxManage debugvm dumpvmcore</title> 144 <remark role="help-copy-synopsis"/> 149 145 <para> 150 146 Creates a system dump file of the specified VM. This file will have … … 164 160 165 161 <refsect2 id="vboxmanage-debugvm-info"> 166 <cmdsynopsis> 167 <command>VBoxManage debugvm</command> 168 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 169 <arg choice="plain">info</arg> 170 <arg choice="req"><replaceable>item</replaceable></arg> 171 <arg rep="repeat"><replaceable>args</replaceable></arg> 172 </cmdsynopsis> 162 <title>VBoxManage debugvm info</title> 163 <remark role="help-copy-synopsis"/> 173 164 <para> 174 165 Displays info items relating to the VMM, device emulations and … … 199 190 200 191 <refsect2 id="vboxmanage-debugvm-injectnmi"> 201 <cmdsynopsis> 202 <command>VBoxManage debugvm</command> 203 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 204 <arg choice="plain">injectnmi</arg> 205 </cmdsynopsis> 192 <title>VBoxManage debugvm injectnmi</title> 193 <remark role="help-copy-synopsis"/> 206 194 <para> 207 195 Causes a non-maskable interrupt (NMI) to be injected into the guest. This … … 213 201 214 202 <refsect2 id="vboxmanage-debugvm-log"> 215 <cmdsynopsis> 216 <command>VBoxManage debugvm</command> 217 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 218 <arg choice="plain">log</arg> 219 <group><arg>--release</arg><arg>--debug</arg></group> 220 <arg rep="repeat"><replaceable>group-settings</replaceable></arg> 221 </cmdsynopsis> 203 <title>VBoxManage debugvm log</title> 204 <remark role="help-copy-synopsis"/> 222 205 <para> 223 206 TODO … … 226 209 227 210 <refsect2 id="vboxmanage-debugvm-logdest"> 228 <cmdsynopsis> 229 <command>VBoxManage debugvm</command> 230 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 231 <arg choice="plain">logdest</arg> 232 <group><arg>--release</arg><arg>--debug</arg></group> 233 <arg rep="repeat"><replaceable>destinations</replaceable></arg> 234 </cmdsynopsis> 211 <title>VBoxManage debugvm logdest</title> 212 <remark role="help-copy-synopsis"/> 235 213 <para> 236 214 TODO … … 239 217 240 218 <refsect2 id="vboxmanage-debugvm-logflags"> 241 <cmdsynopsis> 242 <command>VBoxManage debugvm</command> 243 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 244 <arg choice="plain">logflags</arg> 245 <group><arg>--release</arg><arg>--debug</arg></group> 246 <arg rep="repeat"><replaceable>flags</replaceable></arg> 247 </cmdsynopsis> 219 <title>VBoxManage debugvm logflags</title> 220 <remark role="help-copy-synopsis"/> 248 221 <para> 249 222 TODO … … 252 225 253 226 <refsect2 id="vboxmanage-debugvm-osdetect"> 254 <cmdsynopsis> 255 <command>VBoxManage debugvm</command> 256 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 257 <arg choice="plain">osdetect</arg> 258 </cmdsynopsis> 227 <title>VBoxManage debugvm osdetect</title> 228 <remark role="help-copy-synopsis"/> 259 229 <para> 260 230 Make the VMM's debugger facility (re)-detect the guest operating system (OS). … … 267 237 268 238 <refsect2 id="vboxmanage-debugvm-osinfo"> 269 <cmdsynopsis> 270 <command>VBoxManage debugvm</command> 271 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 272 <arg choice="plain">osinfo</arg> 273 </cmdsynopsis> 239 <title>VBoxManage debugvm osinfo</title> 240 <remark role="help-copy-synopsis"/> 274 241 <para> 275 242 Displays information about the guest operating system (OS) previously … … 279 246 280 247 <refsect2 id="vboxmanage-debugvm-osdmesg"> 281 <cmdsynopsis> 282 <command>VBoxManage debugvm</command> 283 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 284 <arg choice="plain">osdmesg</arg> 285 <arg>--lines <replaceable>lines</replaceable></arg> 286 </cmdsynopsis> 248 <title>VBoxManage debugvm osdmesg</title> 249 <remark role="help-copy-synopsis"/> 287 250 <para> 288 251 Displays the guest OS kernel log, if detected and supported. … … 298 261 299 262 <refsect2 id="vboxmanage-debugvm-getregisters"> 300 <cmdsynopsis> 301 <command>VBoxManage debugvm</command> 302 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 303 <arg choice="plain">getregisters</arg> 304 <arg>--cpu <replaceable>id</replaceable></arg> 305 <arg rep="repeat"><replaceable>reg-set.reg-name</replaceable></arg> 306 </cmdsynopsis> 263 <title>VBoxManage debugvm getregisters</title> 264 <remark role="help-copy-synopsis"/> 307 265 <para> 308 266 Retrieves register values for guest CPUs and emulated devices. … … 333 291 334 292 <refsect2 id="vboxmanage-debugvm-setregisters"> 335 <cmdsynopsis> 336 <command>VBoxManage debugvm</command> 337 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 338 <arg choice="plain">setregisters</arg> 339 <arg>--cpu <replaceable>id</replaceable></arg> 340 <arg rep="repeat"><replaceable>reg-set.reg-name=value</replaceable></arg> 341 </cmdsynopsis> 293 <title>VBoxManage debugvm setregisters</title> 294 <remark role="help-copy-synopsis"/> 342 295 <para> 343 296 Changes register values for guest CPUs and emulated devices. … … 368 321 369 322 <refsect2 id="vboxmanage-debugvm-show"> 370 <cmdsynopsis> 371 <command>VBoxManage debugvm</command> 372 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 373 <arg choice="plain">show</arg> 374 <group><arg>--human-readable</arg><arg>--sh-export</arg><arg>--sh-eval</arg><arg>--cmd-set</arg></group> 375 <arg rep="repeat"><replaceable>settings-item</replaceable></arg> 376 </cmdsynopsis> 323 <title>VBoxManage debugvm show</title> 324 <remark role="help-copy-synopsis"/> 377 325 <para> 378 326 TODO … … 381 329 382 330 <refsect2 id="vboxmanage-debugvm-statistics"> 383 <cmdsynopsis> 384 <command>VBoxManage debugvm</command> 385 <arg choice="req"><replaceable>uuid|vmname</replaceable></arg> 386 <arg choice="plain">statistics</arg> 387 <arg>--reset</arg> 388 <arg>--descriptions</arg> 389 <arg>--pattern <replaceable>pattern</replaceable></arg> 390 </cmdsynopsis> 331 <title>VBoxManage debugvm statistics</title> 332 <remark role="help-copy-synopsis"/> 391 333 <para> 392 334 Displays or resets VMM statistics. -
trunk/doc/manual/en_US/man_VBoxManage_extpack.xml
r56434 r56466 52 52 53 53 <refsect2 id="vboxmanage-extpack-install"> 54 <cmdsynopsis> 55 <command>VBoxManage extpack install</command> 56 <arg>--replace</arg> 57 <arg choice="req"><replaceable>tarball</replaceable></arg> 58 </cmdsynopsis> 54 <title>VBoxManage extpack install</title> 55 <remark role="help-copy-synopsis"/> 59 56 <para> 60 57 Installs a new extension pack on the system. This command will fail if an older … … 77 74 78 75 <refsect2 id="vboxmanage-extpack-uninstall"> 79 <cmdsynopsis> 80 <command>VBoxManage extpack uninstall</command> 81 <arg>--force</arg> 82 <arg choice="req"><replaceable>name</replaceable></arg> 83 </cmdsynopsis> 76 <title>VBoxManage extpack uninstall</title> 77 <remark role="help-copy-synopsis"/> 84 78 <para> 85 79 Uninstalls an extension pack from the system. The subcommand will also succeed … … 105 99 106 100 <refsect2 id="vboxmanage-extpack-cleanup"> 107 <cmdsynopsis> 108 <command>VBoxManage extpack cleanup</command> 109 </cmdsynopsis> 101 <title>VBoxManage extpack cleanup</title> 102 <remark role="help-copy-synopsis"/> 110 103 <para> 111 104 Used to remove temporary files and directories that may have been left behind -
trunk/doc/manual/en_US/user_VBoxManage.xml
r56451 r56466 158 158 for the commands available on your particular host.</para> 159 159 160 <screen> $VBOX_MANAGE_OUTPUT</screen>160 <screen>@VBOX_MANAGE_OUTPUT@</screen> <!-- the whole line is replaced later --> 161 161 <xi:include href="../user_VBoxManage_CommandsOverview.xml" xpointer="element(/1)" 162 162 xmlns:xi="http://www.w3.org/2001/XInclude" /> … … 4254 4254 </sect1> 4255 4255 4256 <sect1 id="vboxmanage-debugvm">4257 <title>VBoxManage debugvm</title>4258 4259 <para>The "debugvm" commands are for experts who want to tinker with the4260 exact details of virtual machine execution. Like the VM debugger described4261 in <xref linkend="ts_debugger" />, these commands are only useful if you are4262 very familiar with the details of the PC architecture and how to debug4263 software.</para>4264 4265 <para>The subcommands of "debugvm" all operate on a running virtual4266 machine. The following are available:<itemizedlist>4267 <listitem>4268 <para>With <computeroutput>dumpguestcore --filename4269 <name></computeroutput>, you can create a system dump of the4270 running VM, which will be written into the given file. This file4271 will have the standard ELF core format (with custom sections); see4272 <xref linkend="ts_guest-core-format" />.</para>4273 4274 <para>This corresponds to the4275 <computeroutput>writecore</computeroutput> command in the debugger.4276 </para>4277 </listitem>4278 4279 <listitem>4280 <para>The <computeroutput>info</computeroutput> command is used to4281 display info items relating to the VMM, device emulations and4282 associated drivers. This command takes one or two arguments: the4283 name of the info item, optionally followed by a string containing4284 arguments specific to the info item.4285 The <computeroutput>help</computeroutput> info item provides a4286 listning of the available items and hints about any optional4287 arguments.</para>4288 4289 <para>This corresponds to the <computeroutput>info</computeroutput>4290 command in the debugger.</para>4291 </listitem>4292 4293 <listitem>4294 <para>The <computeroutput>injectnmi</computeroutput> command causes4295 a non-maskable interrupt (NMI) in the guest, which might be useful4296 for certain debugging scenarios. What happens exactly is dependent4297 on the guest operating system, but an NMI can crash the whole guest4298 operating system. Do not use unless you know what you're4299 doing.</para>4300 </listitem>4301 4302 <listitem>4303 <para>The <computeroutput>osdetect</computeroutput> command makes the4304 VMM's debugger facility (re-)detection the guest operation4305 system.</para>4306 4307 <para>This corresponds to the <computeroutput>detect</computeroutput>4308 command in the debugger.</para>4309 </listitem>4310 4311 <listitem>4312 <para>The <computeroutput>osinfo</computeroutput> command is used to4313 display info about the operating system (OS) detected by the VMM's4314 debugger facility.</para>4315 </listitem>4316 4317 <listitem>4318 <para>The <computeroutput>getregisters</computeroutput> command is4319 used to display CPU and device registers. The command takes a list4320 of registers, each having one of the following forms:4321 <itemizedlist>4322 <listitem><para><computeroutput>register-set.register-name.sub-field</computeroutput></para></listitem>4323 <listitem><para><computeroutput>register-set.register-name</computeroutput></para></listitem>4324 <listitem><para><computeroutput>cpu-register-name.sub-field</computeroutput></para></listitem>4325 <listitem><para><computeroutput>cpu-register-name</computeroutput></para></listitem>4326 <listitem><para><computeroutput>all</computeroutput></para></listitem>4327 </itemizedlist>4328 The <computeroutput>all</computeroutput> form will cause all4329 registers to be shown (no sub-fields). The registers names are4330 case-insensitive. When requesting a CPU register the register set4331 can be omitted, it will be selected using the value of the4332 <computeroutput>--cpu</computeroutput> option (defaulting to 0).4333 </para>4334 </listitem>4335 4336 <listitem>4337 <para>The <computeroutput>setregisters</computeroutput> command is4338 used to change CPU and device registers. The command takes a list4339 of register assignments, each having one of the following forms:4340 <itemizedlist>4341 <listitem><para><computeroutput>register-set.register-name.sub-field=value</computeroutput></para></listitem>4342 <listitem><para><computeroutput>register-set.register-name=value</computeroutput></para></listitem>4343 <listitem><para><computeroutput>cpu-register-name.sub-field=value</computeroutput></para></listitem>4344 <listitem><para><computeroutput>cpu-register-name=value</computeroutput></para></listitem>4345 </itemizedlist>4346 The value format should be in the same style as what4347 <computeroutput>getregisters</computeroutput> displays, with the4348 exception that both octal and decimal can be used instead of4349 hexadecimal. The register naming and the default CPU register set4350 are handled the same way as with the4351 <computeroutput>getregisters</computeroutput> command.</para>4352 </listitem>4353 4354 <listitem>4355 <para>The <computeroutput>statistics</computeroutput> command can be4356 used to display VMM statistics on the command line. The4357 <computeroutput>--reset</computeroutput> option will reset4358 statistics. The affected statistics can be filtered with the4359 <computeroutput>--pattern</computeroutput> option, which accepts4360 DOS/NT-style wildcards (<computeroutput>?</computeroutput> and4361 <computeroutput>*</computeroutput>).</para>4362 </listitem>4363 </itemizedlist></para>4364 </sect1>4365 4366 4256 <sect1 id="metrics"> 4367 4257 <title>VBoxManage metrics</title> … … 4632 4522 </sect1> 4633 4523 4524 <xi:include href="man_VBoxManage_debugvm.xml" xpointer="element(/1)" 4525 xmlns:xi="http://www.w3.org/2001/XInclude" /> 4526 4634 4527 <xi:include href="man_VBoxManage_extpack.xml" xpointer="element(/1)" 4635 4528 xmlns:xi="http://www.w3.org/2001/XInclude" />
Note:
See TracChangeset
for help on using the changeset viewer.