$Date: 2015-06-16 10:58:11 +0000 (Tue, 16 Jun 2015) $ VBoxManage-debugvm 1 VBoxManage-debugvm introspection and guest debugging Oracle VM VirtualBox VBoxManage debugvm uuid|vmname dumpvmcore --filename name VBoxManage debugvm uuid|vmname info item args VBoxManage debugvm uuid|vmname injectnmi VBoxManage debugvm uuid|vmname log --release--debug group-settings VBoxManage debugvm uuid|vmname logdest --release--debug destinations VBoxManage debugvm uuid|vmname logflags --release--debug flags VBoxManage debugvm uuid|vmname osdetect VBoxManage debugvm uuid|vmname osinfo VBoxManage debugvm uuid|vmname osdmesg --lines lines VBoxManage debugvm uuid|vmname getregisters --cpu id reg-set.reg-name VBoxManage debugvm uuid|vmname setregisters --cpu id reg-set.reg-name=value VBoxManage debugvm uuid|vmname show --human-readable--sh-export--sh-eval--cmd-set settings-item VBoxManage debugvm uuid|vmname statistics --reset --descriptions --pattern pattern The "debugvm" commands are for experts who want to tinker with the exact details of virtual machine execution. Like the VM debugger described in , these commands are only useful if you are very familiar with the details of the PC architecture and how to debug software. The subcommands of debugvm all operate on a running virtual machine: uuid|vmname Either the UUID or the name (case sensitive) of a VM. VBoxManage debugvm uuid|vmname dumpvmcore --filename name Creates a system dump file of the specified VM. This file will have the standard ELF core format (with custom sections); see . This corresponds to the writecore command in the debugger. --filename filename The name of the output file. VBoxManage debugvm uuid|vmname info item args Displays info items relating to the VMM, device emulations and associated drivers. This corresponds to the info command in the debugger. info Name of the info item to display. The special name help will list all the available info items and hints about optional arguments. args Optional argument string for the info item handler. Most info items does not take any extra arguments. Arguments not recognized are generally ignored. VBoxManage debugvm uuid|vmname injectnmi Causes a non-maskable interrupt (NMI) to be injected into the guest. This 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. VBoxManage debugvm uuid|vmname log --release--debug group-settings TODO VBoxManage debugvm uuid|vmname logdest --release--debug destinations TODO VBoxManage debugvm uuid|vmname logflags --release--debug flags TODO VBoxManage debugvm uuid|vmname osdetect Make the VMM's debugger facility (re)-detect the guest operating system (OS). This will first load all debugger plug-ins. This corresponds to the detect command in the debugger. VBoxManage debugvm uuid|vmname osinfo Displays information about the guest operating system (OS) previously detected by the VMM's debugger facility. VBoxManage debugvm uuid|vmname osdmesg --lines lines Displays the guest OS kernel log, if detected and supported. --lines lines Number of lines of the log to display, counting from the end. The default is infinite. VBoxManage debugvm uuid|vmname getregisters --cpu id reg-set.reg-name Retrieves register values for guest CPUs and emulated devices. reg-set.reg-name One of more 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. --cpu id Selects the CPU register set when specifying just a CPU register (3rd and 4th form). The default is 0. VBoxManage debugvm uuid|vmname setregisters --cpu id reg-set.reg-name=value Changes register values for guest CPUs and emulated devices. reg-set.reg-name=value One of more register assignment, 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 exception that both octal and decimal can be used instead of hexadecimal. --cpu id Selects the CPU register set when specifying just a CPU register (3rd and 4th form). The default is 0. VBoxManage debugvm uuid|vmname show --human-readable--sh-export--sh-eval--cmd-set settings-item TODO VBoxManage debugvm uuid|vmname statistics --reset --descriptions --pattern pattern Displays or resets VMM statistics. Retrieves register values for guest CPUs and emulated devices. --pattern pattern DOS/NT-style wildcards patterns for selecting statistics. Multiple patterns can be specified by using the '|' (pipe) character as separator. --reset Select reset instead of display mode.