clonevm --groups does not create new group

[BrianNixon]

VBoxManage clonevm VM1 --groups /NewGroup --register successfully clones and registers VM1 (placing it in a subdirectory NewGroup), but does not create the group /NewGroup. (VBoxManage list groups does not show the new group.)

[Socratis]

Confirming.

Host	OSX 10.11.6
VirtualBox	5.2.11r122202

The alternative/workaround is to clone the VM and then assign it to a group. Then the group gets properly created. As in:

VBoxManage clonevm VM1 --register
VBoxManage modifyvm VM1 --groups /NewGroup

It's definitely a bug. Another thing that surprised me while I was researching this, is that there is no "VBoxManage groups" sub-command to manage groups.

I would expect to be able to create and delete groups at will, list its members, etc. I'll work out the options that I think should be there and post them later.

[Socratis]

Here's the proposed "VBoxManage groups" sub-command structure that I believe should be there:

VBoxManage groups add <group_name> |
                  delete <group_name> |
                  members <group_name>          (or: list <group_name>)

• The "add" option would add a group named "<group_name>".
• The "delete" option would remove a group named "<group_name>". All VMs that were part of the group return to the default "/" group.
• The "members" (or "list") option would list all VMs that are members of that "<group_name>".

At this point my biggest concern would be the changes that it would require to the "VirtualBox.xml" file to accommodate the existence of a group (or more) with potentially no members at all. But I don't know the source code by heart... ;)

And of course fix the original problem in the report, the "VBoxManage clonevm <VM> --groups <group_name>", so that "<group_name>" is indeed created.