The details about the direction of the merge and its implication is described in Merge operating modes below. The default is to merge the virtual machine into its parent (equivalent to -p).
vmhome_path must be a valid virtual machine home directory. If no value is provided, the current working directory is assumed.
Merge operating modes
Merge operating modes are exclusive.
If each affected virtual machine is organized as a subdirectory of its parent, the directories are moved as required to reflect the updated parent-child relationship.
The merge method selection options are as follows:
Merge the virtual machine into its child.
The virtual machine located in vmhome_path must have at least one child.
This method merges the storage and settings of the virtual machine located in vmhome_path into its child(s) and then deletes it, moving the child(s) as necessary. If the original virtual machine had a parent, it now becomes the parent of the child(s) virtual machine.
If the virtual machine located in vmhome_path has more than one child, safe merging (see -s) is automatically enabled. This may induce a longer time to process the merge.
If the virtual machine located in vmhome_path has no parent, its child will become root of the virtual machine hierarchy tree. If there is several childs, each one will become root of their own tree, becoming unrelated to each other. In this situation, unless -y has been used an interactive confirmation is required before proceeding.
Merge the virtual machine into its parent (default behavior).
The virtual machine located in vmhome_path must have a parent and be its only child.
This method merges the storage and settings of the virtual machine located in vmhome_path into its parent and then deletes it. If the original virtual machine had any child, they now become childs of the resulting parent virtual machine.
The other options are as follows:
Show usage information summary then exit.
Decrease verbosity. Add several -q options to decrease verbosity even more (-qq by default to get minimal output). See vmtools.conf(5) for more information about verbosity levels.
See -v to increase the verbosity level.
Enable safe merging.
By default, vmmerge attempts to apply a fast merging algorithm where the content of the virtual machine storage image is directly merged. The downside of this is that in case of an error, it becomes impossible to completely rollback to the previous state as the content of the image files has already be merged. This however does not break any virtual machine (the parent and child virtual machines simply have an identical storage content) and is usually acceptable in regards to the benefits.
When safe mode is enabled, vmmerge only operates on copies of the storage image files during the merging process. In case of error, this allows a complete rollback to the previous state. The downside of this is that storage images are often large files and copying them may therefore require time and disk space, making virtual machines merging a heavy and slow process.
Note that for implemenation reasons safe mode is automatically enabled when child-merging a virtual machines with several childs.
Increase verbosity. Add several -v options to increase verbosity even more (-vvv by default to get the most verbose output, including debugging messages). See vmtools.conf(5) for more information about verbosity levels.
See -q to decrease the verbosity level.
Don’t ask any question: accept all confirmation requests and automatically select the default answer in any other situation.
Use this option with great care: no confirmation will be asked before deleting or overwriting any files!
Default location to store temporary files, by default /tmp.
Location of user’s configuration files, by default ~/.config.
Libraries shared by the vmtools project utilities.