8 VBoxManage help info item provides a listning of the available items and hints about any optional arguments. This corresponds to the info command in the debugger. • The injectnmi command causes a non-maskable interrupt (NMI) in the guest, which might be useful for certain debugging scenarios. What happens exactly is dependent on the guest operating system, but an NMI can crash the whole guest operating system. Do not use unless you know what you’re doing. • The osdetect command makes the VMM’s debugger facility (re-)detection the guest oper- ation system. This corresponds to the detect command in the debugger. • The osinfo command is used to display info about the operating system (OS) detected by the VMM’s debugger facility. • The getregisters command is used to display CPU and device registers. The command takes a list of registers, each having one of the following forms: – register-set.register-name.sub-field – register-set.register-name – cpu-register-name.sub-field – cpu-register-name – all The all form will cause all registers to be shown (no sub-fields). The registers names are case-insensitive. When requesting a CPU register the register set can be omitted, it will be selected using the value of the --cpu option (defaulting to 0). • The setregisters command is used to change CPU and device registers. The command takes a list of register assignments, each having one of the following forms: – register-set.register-name.sub-field=value – register-set.register-name=value – cpu-register-name.sub-field=value – cpu-register-name=value The value format should be in the same style as what getregisters displays, with the ex- ception that both octal and decimal can be used instead of hexadecimal. The register nam- ing and the default CPU register set are handled the same way as with the getregisters command. • The statistics command can be used to display VMM statistics on the command line. The --reset option will reset statistics. The affected statistics can be filtered with the --pattern option, which accepts DOS/NT-style wildcards (? and *). 8.31 VBoxManage metrics This command supports monitoring the usage of system resources. Resources are represented by various metrics associated with the host system or a particular VM. For example, the host system has a CPU/Load/User metric that shows the percentage of time CPUs spend executing in user mode over a specific sampling period. Metric data is collected and retained internally it may be retrieved at any time with the VBoxManage metrics query subcommand. The data is available as long as the background VBoxSVC process is alive. That process terminates shortly after all VMs and frontends have been closed. 130