Index: /trunk/doc/manual/en_US/user_VBoxManage.xml
===================================================================
--- /trunk/doc/manual/en_US/user_VBoxManage.xml (revision 35284)
+++ /trunk/doc/manual/en_US/user_VBoxManage.xml (revision 35285)
@@ -1397,4 +1397,14 @@
cable on a physical machine, and should be avoided if possible.
+
+
+ VBoxManage adoptstate
+
+ If you have a saved state file (.sav)
+ that is seperate from the VM configuration, you can use this command to
+ "adopt" the file. This will change the VM to saved state and when you
+ start it, VirtualBox will attempt to restore it from the saved state file
+ you indicated. This command should only be used in special setups.
+
@@ -1443,98 +1453,21 @@
-
- VBoxManage storagectl
-
- This command attaches/modifies/removes a storage controller. After
- this, virtual media can be attached to the controller with the
- storageattach command (see the next
- section).
-
- The syntax is as follows:
-
- VBoxManage storagectl <uuid|vmname>
- --name <name>
- [--add <ide/sata/scsi/floppy>]
- [--controller <LsiLogic/BusLogic/IntelAhci/PIIX3/
- PIIX4/ICH6/I8207>]
- [--sataideemulation<1-4> <1-30>]
- [--sataportcount <1-30>]
- [--hostiocache on|off]
- [--remove]
-
- where the parameters mean:
-
- uuid|vmname
-
-
- The VM UUID or VM Name. Mandatory.
-
-
-
-
- name
-
-
- Name of the storage controller. Mandatory.
-
-
-
-
- add
-
-
- Define the type of the system bus to which the storage
- controller must be connected.
-
-
-
-
- controller
-
-
- Allows to choose the type of chipset being emulated for the
- given storage controller.
-
-
-
-
- sataideemulation
-
-
- This specifies which SATA ports should operate in IDE
- emulation mode. As explained in , by default, this is the case for
- SATA ports 1-4; with this command, you can map four IDE channels
- to any of the 30 supported SATA ports.
-
-
-
-
- sataportcount
-
-
- This determines how many ports the SATA controller should
- support.
-
-
-
-
- hostiocache
-
-
- Configures the use of the host I/O cache for all disk images
- attached to this storage controller. For details, please see .
-
-
-
-
- remove
-
-
- Removes the storage controller from the VM config.
-
-
-
+
+ VBoxManage closemedium
+
+ This commands removes a hard disk, DVD or floppy image from a
+ VirtualBox media registry.
+ Before VirtualBox 4.0, it was necessary to call VBoxManage
+ openmedium before a medium could be attached to a virtual machine;
+ that call "registered" the medium with the global VirtualBox media
+ registry. With VirtualBox 4.0 this is no longer necessary; media are
+ added to media registries automatically. The "closemedium" call has
+ been retained, however, to allow for explicitly removing a medium from
+ a registry.
+
+
+ Optionally, you can request that the image be deleted. You will get
+ appropriate diagnostics that the deletion failed, however the image will
+ become unregistered in any case.
@@ -1790,4 +1723,100 @@
+
+
+ VBoxManage storagectl
+
+ This command attaches/modifies/removes a storage controller. After
+ this, virtual media can be attached to the controller with the
+ storageattach command (see the next
+ section).
+
+ The syntax is as follows:
+
+ VBoxManage storagectl <uuid|vmname>
+ --name <name>
+ [--add <ide/sata/scsi/floppy>]
+ [--controller <LsiLogic/BusLogic/IntelAhci/PIIX3/
+ PIIX4/ICH6/I8207>]
+ [--sataideemulation<1-4> <1-30>]
+ [--sataportcount <1-30>]
+ [--hostiocache on|off]
+ [--remove]
+
+ where the parameters mean:
+
+ uuid|vmname
+
+
+ The VM UUID or VM Name. Mandatory.
+
+
+
+
+ name
+
+
+ Name of the storage controller. Mandatory.
+
+
+
+
+ add
+
+
+ Define the type of the system bus to which the storage
+ controller must be connected.
+
+
+
+
+ controller
+
+
+ Allows to choose the type of chipset being emulated for the
+ given storage controller.
+
+
+
+
+ sataideemulation
+
+
+ This specifies which SATA ports should operate in IDE
+ emulation mode. As explained in , by default, this is the case for
+ SATA ports 1-4; with this command, you can map four IDE channels
+ to any of the 30 supported SATA ports.
+
+
+
+
+ sataportcount
+
+
+ This determines how many ports the SATA controller should
+ support.
+
+
+
+
+ hostiocache
+
+
+ Configures the use of the host I/O cache for all disk images
+ attached to this storage controller. For details, please see .
+
+
+
+
+ remove
+
+
+ Removes the storage controller from the VM config.
+
+
+
+
@@ -2081,23 +2110,4 @@
"convertfromraw" command.
-
-
-
- VBoxManage closemedium
-
- This commands removes a hard disk, DVD or floppy image from a
- VirtualBox media registry.
- Before VirtualBox 4.0, it was necessary to call VBoxManage
- openmedium before a medium could be attached to a virtual machine;
- that call "registered" the medium with the global VirtualBox media
- registry. With VirtualBox 4.0 this is no longer necessary; media are
- added to media registries automatically. The "closemedium" call has
- been retained, however, to allow for explicitly removing a medium from
- a registry.
-
-
- Optionally, you can request that the image be deleted. You will get
- appropriate diagnostics that the deletion failed, however the image will
- become unregistered in any case.
@@ -2244,4 +2254,550 @@
+
+ VBoxManage guestproperty
+
+ The "guestproperty" commands allow you to get or set properties of a
+ running virtual machine. Please see
+ for an introduction. As explained there, guest properties are arbitrary
+ key/value string pairs which can be written to and read from by either the
+ guest or the host, so they can be used as a low-volume communication
+ channel for strings, provided that a guest is running and has the Guest
+ Additions installed. In addition, a number of values whose keys begin with
+ "/VirtualBox/" are automatically set and maintained by the Guest
+ Additions.
+
+ The following subcommands are available (where
+ <vm>, in each case, can either be a
+ VM name or a VM UUID, as with the other VBoxManage commands):
+
+ enumerate <vm> [--patterns
+ <pattern>]: This lists all the guest
+ properties that are available for the given VM, including the value.
+ This list will be very limited if the guest's service process cannot
+ be contacted, e.g. because the VM is not running or the Guest
+ Additions are not installed.
+
+ If --patterns <pattern>
+ is specified, it acts as a filter to only list properties that match
+ the given pattern. The pattern can contain the following wildcard
+ characters:
+
+ * (asterisk):
+ represents any number of characters; for example,
+ "/VirtualBox*" would match
+ all properties beginning with "/VirtualBox".
+
+
+
+ ? (question mark):
+ represents a single arbitrary character; for example,
+ "fo?" would match both "foo"
+ and "for".
+
+
+
+ | (pipe symbol): can be
+ used to specify multiple alternative patterns; for example,
+ "s*|t*" would match anything
+ starting with either "s" or "t".
+
+
+
+
+
+ get <vm>: This
+ retrieves the value of a single property only. If the property
+ cannot be found (e.g. because the guest is not running), this will
+ print "No value set!".
+
+
+
+ set <vm> <property> [<value>
+ [--flags <flags>]]: This allows you to set a
+ guest property by specifying the key and value. If
+ <value> is omitted, the
+ property is deleted. With --flags
+ you can optionally specify additional behavior (you can combine
+ several by separating them with commas):
+
+ TRANSIENT: the value
+ will not be stored with the VM data when the VM exits;
+
+
+
+ RDONLYGUEST: the value
+ can only be changed by the host, but the guest can only read
+ it;
+
+
+
+ RDONLYHOST: reversely,
+ the value can only be changed by the guest, but the host can
+ only read it;
+
+
+
+ READONLY: a combination
+ of the two, the value cannot be changed at all.
+
+
+
+
+
+ wait <vm> <pattern> --timeout
+ <timeout>: This waits for a particular value
+ described by "pattern" to change or to be deleted or created. The
+ pattern rules are the same as for the "enumerate" subcommand
+ above.
+
+
+
+
+
+ VBoxManage guestcontrol
+
+ The "guestcontrol" commands allow you to control certain things
+ inside a guest from the host. Please see for an introduction.
+
+ Generally, the syntax is as follows:
+
+ VBoxManage guestcontrol <command>
+
+ The following subcommands are available (where
+ <vm>, in each case, can either be a
+ VM name or a VM UUID, as with the other VBoxManage commands):
+
+ execute, which allows for
+ executing a program/script (process) which is already installed and
+ runnable on the guest. This command only works while a VM is up and
+ running and has the following syntax:
+
+ VBoxManage guestcontrol exec[ute] <vmname>|<uuid>
+ <path to program>
+ --username <name> --password <password>
+ [--arguments "<arguments>"]
+ [--environment "<NAME>=<VALUE> [<NAME>=<VALUE>]"]
+ [--flags <flags>] [--timeout <msec>]
+ [--verbose] [--wait-for exit,stdout,stderr||]
+
+ where the parameters mean:
+
+ uuid|vmname
+
+
+ The VM UUID or VM name. Mandatory.
+
+
+
+
+ path to program
+
+
+ Absolute path and process name of process to execute
+ in the guest, e.g.
+ C:\Windows\System32\calc.exe
+
+
+
+
+ --arguments "<arguments>"
+
+
+ One or more arguments to pass to the process being
+ executed.
+
+ Arguments containing spaces must be enclosed in
+ quotation marks. More than one
+ --arguments at a time can
+ be specified to keep the command line tidy.
+
+
+
+
+ --environment
+ "<NAME>=<VALUE>"
+
+
+ One or more environment variables to be set or
+ unset.
+
+ By default, the new process in the guest will be
+ created with the standard environment of the guest OS. This
+ option allows for modifying that environment. To set/modify
+ a variable, a pair of
+ NAME=VALUE must be
+ specified; to unset a certain variable, the name with no
+ value must set, e.g.
+ NAME=.
+
+ Arguments containing spaces must be enclosed in
+ quotation marks. More than one
+ --environment at a time can
+ be specified to keep the command line tidy.
+
+
+
+
+ --flags <flags>
+
+
+ Additional flags to set. This is not used at the
+ moment.
+
+
+
+
+ --timeout <msec>
+
+
+ Value (in milliseconds) that specifies the time how
+ long the started process is allowed to run and how long
+ VBoxManage waits for getting output from that process. If no
+ timeout is specified, VBoxManage will wait forever until the
+ started process ends or an error occured.
+
+
+
+
+ --username <name>
+
+
+ Name of the user the process should run under. This
+ user must exist on the guest OS.
+
+
+
+
+ --password <password>
+
+
+ Password of the user account specified with
+ --username. If not given,
+ an empty password is assumed.
+
+
+
+
+ --verbose
+
+
+ Tells VBoxManage to be more verbose.
+
+
+
+
+ --wait-for <action>
+
+
+ Tells VBoxManage to wait for a certain action to
+ happen and react to it. The following actions are available:
+
+
+ exit
+
+
+ Waits until the process ends and outputs its
+ exit code along with the exit reason/flags.
+
+
+
+
+ stdout or stderr
+
+
+ Waits until the process ends and outputs its
+ exit code along with the exit reason/flags. After
+ that VBoxManage retrieves the output collected from
+ the guest process's stdout and stderr.
+
+
+
+
+
+
+
+
+ On Windows there are certain limitations for graphical
+ applications; please see for more
+ information.
+ Examples: VBoxManage --nologo guestcontrol execute "My VM" "/bin/ls" --arguments "-l /usr"
+ --username foo --password bar --wait-for stdout VBoxManage --nologo guestcontrol execute "My VM" "c:\\windows\\system32\\ipconfig.exe"
+ --username foo --password bar --wait-for stdout Note that
+ the double backslashes in the second example are only required on
+ Unix hosts.
+
+
+
+ copyto, which allows copying
+ files from the host to the guest (only with installed Guest
+ Additions 4.0 and later).
+
+ VBoxManage copyto|cp <vmname>|<uuid>
+ <source on host> <destination on guest>
+ --username <name> --password <password>
+ [--dryrun] [--follow] [--recursive] [--verbose]
+
+ where the parameters mean:
+
+ uuid|vmname
+
+
+ The VM UUID or VM name. Mandatory.
+
+
+
+
+ source on host
+
+
+ Absolute path of source file(s) on host to copy over
+ to the guest, e.g.
+ C:\Windows\System32\calc.exe.
+ This also can be a wildcard expression, e.g.
+ C:\Windows\System32\*.dll
+
+
+
+
+ destination on guest
+
+
+ Absolute destination path on the guest, e.g.
+ C:\Temp
+
+
+
+
+ --username <name>
+
+
+ Name of the user the copy process should run under.
+ This user must exist on the guest OS.
+
+
+
+
+ --password <password>
+
+
+ Password of the user account specified with
+ --username. If not given,
+ an empty password is assumed.
+
+
+
+
+ --dryrun
+
+
+ Tells VBoxManage to only perform a dry run instead of
+ really copying files to the guest.
+
+
+
+
+ --follow
+
+
+ Enables following symlinks on the host's
+ source.
+
+
+
+
+ --recursive
+
+
+ Recursively copies files/directories of the specified
+ source.
+
+
+
+
+ --verbose
+
+
+ Tells VBoxManage to be more verbose.
+
+
+
+
+ --flags <flags>
+
+
+ Additional flags to set. This is not used at the
+ moment.
+
+
+
+
+
+
+ createdirectory, which allows
+ copying files from the host to the guest (only with installed Guest
+ Additions 4.0 and later).
+
+ VBoxManage createdir[ectory]|mkdir|md <vmname>|<uuid>
+ <directory to create on guest>
+ [--username "<name>"] [--password "<password>"]
+ [--parents] [--mode <mode>] [--verbose]
+
+ where the parameters mean:
+
+ uuid|vmname
+
+
+ The VM UUID or VM name. Mandatory.
+
+
+
+
+ directory to create on guest
+
+
+ Absolute path of directory/directories to create on
+ guest, e.g. D:\Foo\Bar.
+ Parent directories need to exist (e.g. in this example
+ D:\Foo) when switch
+ --parents is omitted. The
+ specified user must have appropriate rights to create the
+ specified directory.
+
+
+
+
+ --username <name>
+
+
+ Name of the user the copy process should run under.
+ This user must exist on the guest OS.
+
+
+
+
+ --password <password>
+
+
+ Password of the user account specified with
+ --username. If not given,
+ an empty password is assumed.
+
+
+
+
+ --parents
+
+
+ Also creates not yet existing parent directories of
+ the specified directory, e.g. if the directory
+ D:\Foo of
+ D:\Foo\Bar does not exist
+ yet it will be created. Without specifying
+ --parent the action would
+ have failed.
+
+
+
+
+ --mode <mode>
+
+
+ Sets the permission mode of the specified directory.
+ Only octal modes (e.g.
+ 0755) are supported right
+ now.
+
+
+
+
+ --verbose
+
+
+ Tells VBoxManage to be more verbose.
+
+
+
+
+
+
+ updateadditions, which allows
+ for updating an already installed Guest Additions version on the
+ guest (only already installed Guest Additions 4.0 and later).
+
+ VBoxManage guestcontrol updateadditions <vmname>|<uuid>
+ [--source "<guest additions .ISO file to use>"] [--verbose]
+
+ where the parameters mean:
+
+ uuid|vmname
+
+
+ The VM UUID or VM name. Mandatory.
+
+
+
+
+ --source "<guest additions .ISO file to
+ use>"
+
+
+ Full path to an alternative VirtualBox Guest Additions
+ .ISO file to use for the Guest Additions update.
+
+
+
+
+ --verbose
+
+
+ Tells VBoxManage to be more verbose.
+
+
+
+
+
+
+
+
+ VBoxManage debugvm
+
+ 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. The following are available:
+
+ With dumpguestcore --filename
+ <name>, you can create a system dump of the
+ running VM, which will be written into the given file. This file
+ will have the standard ELF core format (with custom sections); see
+ .
+
+
+
+ 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 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
+ *).
+
+
+
+
VBoxManage metrics
@@ -2398,549 +2954,13 @@
-
-
- VBoxManage guestproperty
-
- The "guestproperty" commands allow you to get or set properties of a
- running virtual machine. Please see
- for an introduction. As explained there, guest properties are arbitrary
- key/value string pairs which can be written to and read from by either the
- guest or the host, so they can be used as a low-volume communication
- channel for strings, provided that a guest is running and has the Guest
- Additions installed. In addition, a number of values whose keys begin with
- "/VirtualBox/" are automatically set and maintained by the Guest
- Additions.
-
- The following subcommands are available (where
- <vm>, in each case, can either be a
- VM name or a VM UUID, as with the other VBoxManage commands):
-
- enumerate <vm> [--patterns
- <pattern>]: This lists all the guest
- properties that are available for the given VM, including the value.
- This list will be very limited if the guest's service process cannot
- be contacted, e.g. because the VM is not running or the Guest
- Additions are not installed.
-
- If --patterns <pattern>
- is specified, it acts as a filter to only list properties that match
- the given pattern. The pattern can contain the following wildcard
- characters:
-
- * (asterisk):
- represents any number of characters; for example,
- "/VirtualBox*" would match
- all properties beginning with "/VirtualBox".
-
-
-
- ? (question mark):
- represents a single arbitrary character; for example,
- "fo?" would match both "foo"
- and "for".
-
-
-
- | (pipe symbol): can be
- used to specify multiple alternative patterns; for example,
- "s*|t*" would match anything
- starting with either "s" or "t".
-
-
-
-
-
- get <vm>: This
- retrieves the value of a single property only. If the property
- cannot be found (e.g. because the guest is not running), this will
- print "No value set!".
-
-
-
- set <vm> <property> [<value>
- [--flags <flags>]]: This allows you to set a
- guest property by specifying the key and value. If
- <value> is omitted, the
- property is deleted. With --flags
- you can optionally specify additional behavior (you can combine
- several by separating them with commas):
-
- TRANSIENT: the value
- will not be stored with the VM data when the VM exits;
-
-
-
- RDONLYGUEST: the value
- can only be changed by the host, but the guest can only read
- it;
-
-
-
- RDONLYHOST: reversely,
- the value can only be changed by the guest, but the host can
- only read it;
-
-
-
- READONLY: a combination
- of the two, the value cannot be changed at all.
-
-
-
-
-
- wait <vm> <pattern> --timeout
- <timeout>: This waits for a particular value
- described by "pattern" to change or to be deleted or created. The
- pattern rules are the same as for the "enumerate" subcommand
- above.
-
-
-
-
-
- VBoxManage guestcontrol
-
- The "guestcontrol" commands allow you to control certain things
- inside a guest from the host. Please see for an introduction.
-
- Generally, the syntax is as follows:
-
- VBoxManage guestcontrol <command>
-
- The following subcommands are available (where
- <vm>, in each case, can either be a
- VM name or a VM UUID, as with the other VBoxManage commands):
-
- execute, which allows for
- executing a program/script (process) which is already installed and
- runnable on the guest. This command only works while a VM is up and
- running and has the following syntax:
-
- VBoxManage guestcontrol exec[ute] <vmname>|<uuid>
- <path to program>
- --username <name> --password <password>
- [--arguments "<arguments>"]
- [--environment "<NAME>=<VALUE> [<NAME>=<VALUE>]"]
- [--flags <flags>] [--timeout <msec>]
- [--verbose] [--wait-for exit,stdout,stderr||]
-
- where the parameters mean:
-
- uuid|vmname
-
-
- The VM UUID or VM name. Mandatory.
-
-
-
-
- path to program
-
-
- Absolute path and process name of process to execute
- in the guest, e.g.
- C:\Windows\System32\calc.exe
-
-
-
-
- --arguments "<arguments>"
-
-
- One or more arguments to pass to the process being
- executed.
-
- Arguments containing spaces must be enclosed in
- quotation marks. More than one
- --arguments at a time can
- be specified to keep the command line tidy.
-
-
-
-
- --environment
- "<NAME>=<VALUE>"
-
-
- One or more environment variables to be set or
- unset.
-
- By default, the new process in the guest will be
- created with the standard environment of the guest OS. This
- option allows for modifying that environment. To set/modify
- a variable, a pair of
- NAME=VALUE must be
- specified; to unset a certain variable, the name with no
- value must set, e.g.
- NAME=.
-
- Arguments containing spaces must be enclosed in
- quotation marks. More than one
- --environment at a time can
- be specified to keep the command line tidy.
-
-
-
-
- --flags <flags>
-
-
- Additional flags to set. This is not used at the
- moment.
-
-
-
-
- --timeout <msec>
-
-
- Value (in milliseconds) that specifies the time how
- long the started process is allowed to run and how long
- VBoxManage waits for getting output from that process. If no
- timeout is specified, VBoxManage will wait forever until the
- started process ends or an error occured.
-
-
-
-
- --username <name>
-
-
- Name of the user the process should run under. This
- user must exist on the guest OS.
-
-
-
-
- --password <password>
-
-
- Password of the user account specified with
- --username. If not given,
- an empty password is assumed.
-
-
-
-
- --verbose
-
-
- Tells VBoxManage to be more verbose.
-
-
-
-
- --wait-for <action>
-
-
- Tells VBoxManage to wait for a certain action to
- happen and react to it. The following actions are available:
-
-
- exit
-
-
- Waits until the process ends and outputs its
- exit code along with the exit reason/flags.
-
-
-
-
- stdout or stderr
-
-
- Waits until the process ends and outputs its
- exit code along with the exit reason/flags. After
- that VBoxManage retrieves the output collected from
- the guest process's stdout and stderr.
-
-
-
-
-
-
-
-
- On Windows there are certain limitations for graphical
- applications; please see for more
- information.
- Examples: VBoxManage --nologo guestcontrol execute "My VM" "/bin/ls" --arguments "-l /usr"
- --username foo --password bar --wait-for stdout VBoxManage --nologo guestcontrol execute "My VM" "c:\\windows\\system32\\ipconfig.exe"
- --username foo --password bar --wait-for stdout Note that
- the double backslashes in the second example are only required on
- Unix hosts.
-
-
-
- copyto, which allows copying
- files from the host to the guest (only with installed Guest
- Additions 4.0 and later).
-
- VBoxManage copyto|cp <vmname>|<uuid>
- <source on host> <destination on guest>
- --username <name> --password <password>
- [--dryrun] [--follow] [--recursive] [--verbose]
-
- where the parameters mean:
-
- uuid|vmname
-
-
- The VM UUID or VM name. Mandatory.
-
-
-
-
- source on host
-
-
- Absolute path of source file(s) on host to copy over
- to the guest, e.g.
- C:\Windows\System32\calc.exe.
- This also can be a wildcard expression, e.g.
- C:\Windows\System32\*.dll
-
-
-
-
- destination on guest
-
-
- Absolute destination path on the guest, e.g.
- C:\Temp
-
-
-
-
- --username <name>
-
-
- Name of the user the copy process should run under.
- This user must exist on the guest OS.
-
-
-
-
- --password <password>
-
-
- Password of the user account specified with
- --username. If not given,
- an empty password is assumed.
-
-
-
-
- --dryrun
-
-
- Tells VBoxManage to only perform a dry run instead of
- really copying files to the guest.
-
-
-
-
- --follow
-
-
- Enables following symlinks on the host's
- source.
-
-
-
-
- --recursive
-
-
- Recursively copies files/directories of the specified
- source.
-
-
-
-
- --verbose
-
-
- Tells VBoxManage to be more verbose.
-
-
-
-
- --flags <flags>
-
-
- Additional flags to set. This is not used at the
- moment.
-
-
-
-
-
-
- createdirectory, which allows
- copying files from the host to the guest (only with installed Guest
- Additions 4.0 and later).
-
- VBoxManage createdir[ectory]|mkdir|md <vmname>|<uuid>
- <directory to create on guest>
- [--username "<name>"] [--password "<password>"]
- [--parents] [--mode <mode>] [--verbose]
-
- where the parameters mean:
-
- uuid|vmname
-
-
- The VM UUID or VM name. Mandatory.
-
-
-
-
- directory to create on guest
-
-
- Absolute path of directory/directories to create on
- guest, e.g. D:\Foo\Bar.
- Parent directories need to exist (e.g. in this example
- D:\Foo) when switch
- --parents is omitted. The
- specified user must have appropriate rights to create the
- specified directory.
-
-
-
-
- --username <name>
-
-
- Name of the user the copy process should run under.
- This user must exist on the guest OS.
-
-
-
-
- --password <password>
-
-
- Password of the user account specified with
- --username. If not given,
- an empty password is assumed.
-
-
-
-
- --parents
-
-
- Also creates not yet existing parent directories of
- the specified directory, e.g. if the directory
- D:\Foo of
- D:\Foo\Bar does not exist
- yet it will be created. Without specifying
- --parent the action would
- have failed.
-
-
-
-
- --mode <mode>
-
-
- Sets the permission mode of the specified directory.
- Only octal modes (e.g.
- 0755) are supported right
- now.
-
-
-
-
- --verbose
-
-
- Tells VBoxManage to be more verbose.
-
-
-
-
-
-
- updateadditions, which allows
- for updating an already installed Guest Additions version on the
- guest (only already installed Guest Additions 4.0 and later).
-
- VBoxManage guestcontrol updateadditions <vmname>|<uuid>
- [--source "<guest additions .ISO file to use>"] [--verbose]
-
- where the parameters mean:
-
- uuid|vmname
-
-
- The VM UUID or VM name. Mandatory.
-
-
-
-
- --source "<guest additions .ISO file to
- use>"
-
-
- Full path to an alternative VirtualBox Guest Additions
- .ISO file to use for the Guest Additions update.
-
-
-
-
- --verbose
-
-
- Tells VBoxManage to be more verbose.
-
-
-
-
-
-
-
-
- VBoxManage debugvm
-
- 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. The following are available:
-
- With dumpguestcore --filename
- <name>, you can create a system dump of the
- running VM, which will be written into the given file. This file
- will have the standard ELF core format (with custom sections); see
- .
-
-
-
- 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 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
- *).
-
-
+
+
+ VBoxManage hostonlyif
+
+ With "hostonlyif" you can change the IP configuration of a host-only
+ network interface. For a description of host-only networking, please
+ refer to . Each host-only interface is
+ identified by a name and can either use the internal DHCP server or a
+ manual IP configuration (both IP4 and IP6).