"Group" in VirtualBox GUI = VM's inaccessible from cmdline

[ToddG]

Adding VM's to "Groups" from the VirtualBox UI makes VM's inaccessible for command line tools?

VirtualBox 4.2.16 on Solaris 11x64

When adding a set of VM's to a "group", the actual VM is moved from its original location to a sub-path based on the group name (why?). This appears to mess up access to the VM's for the command line tools like VBoxManage and VBoxHeadless...

tgrayson@sol11x64:~$ sudo /opt/VirtualBox/VBoxManage list vms
"OEL6u3x64-hd0" {1b243d15-d5ae-406e-8002-b2f10b2ed2ee}
"OEL6u3x64-hd1" {b901da8b-752c-422e-8f4a-1f3b20c6bdb2}
"OEL6u3x64-hd2" {101363db-ad51-4602-a42d-8635838bea6f}
"OEL6u3x64-hd3" {a21f27c2-a4d4-4492-95ab-879988abd54c}
"OEL6u3x64-hd4" {7c527c3e-835d-407a-9e3e-2c227d8c11a1}
"<inaccessible>" {675a40fe-159d-4a0f-a688-e853f0a1d0b8}
"<inaccessible>" {a5ddced5-e859-4374-b144-31cf7683bc5a}
"<inaccessible>" {89b79921-e7f6-4ef0-875b-fd68c2facbb0}
"<inaccessible>" {c7d3e233-ae77-44b8-abd4-6537611541c8}
"<inaccessible>" {0dd42b62-331f-4cff-839e-fcfb7139eff6}
"<inaccessible>" {5c72f31a-0825-44df-ab2b-59211a0f6752}
"Win2k8x64-AD2" {69ca8e70-2332-46b5-909f-80be2e1a513e}
"<inaccessible>" {15aba92a-4c41-4d1b-96db-89f0b9341b4c}
"<inaccessible>" {e5e2a06d-1959-40c5-a9a8-aa48c0e4dee1}
"<inaccessible>" {445f73b6-9541-455c-92fd-999682aad4c2}
"<inaccessible>" {aee85677-be87-457f-980f-3565a28fb5c0}
"cm-tripwire.test.lab" {bf6b35ec-87dc-45eb-972b-7b4f7e735be0}
"win2012x64" {44fb14ee-1ca4-42b0-bab9-75a89c8c27f9}
"<inaccessible>" {cddf758e-8111-46a6-86fc-6d331f11062d}
"<inaccessible>" {0496b28e-52c7-401f-a8c8-90816fb059fe}
"<inaccessible>" {fc42fb85-a2ad-4094-8395-6b01c4840a1c}
"<inaccessible>" {a980a098-cbd8-4b60-ab3a-dd4b6fff6ca3}
"<inaccessible>" {88b8424b-738d-4ac8-8246-8aac4e008a20}
"<inaccessible>" {082b5468-36d3-4541-87b6-56213020d2cd}
"<inaccessible>" {c268dd3c-7e91-445e-b0b6-327703fb4ac9}

Moving the vm's back out of the "Group" sub-path (directory) to their original path seems to fix things. Looks like the "groups" function in the UI is unstable?

Thanks

ToddG

[ToddG]

Oh I mis-spoke - everythings still hosed after moving the VM's back? This is a mess!

[ToddG]

So FYI - anyone that runs into this

You have to remove the VM and then re-add it, removing it from its group to clean this up, after copying the VM from its group folder back to its original location.

I suggest anyone using virtualbox to manage vm's to avoid groups altogether right now, IMHO completely unstable.