Default VM storage location should not contain a whitespace in the name and images and VMs should be stored separately

[mark_orion]

I suggest going back to the old (Version 3>) way of storing diskimages and VMs in different directories by default. The new way of creating the VM and the diskimage in the same place makes no sense on a system that allows to share diskimages between VMs. And I would suggest to not use a whitespace in the new default location "VirtualBox VMs" this makes it more difficult to work from the command line.

[Christian Pötzsch]

Sorry, this decision was done with many internal discussions and will not be reverted. Btw, you can move your disk images to whatever directory you want and reattach it to the VM using it. You can also overwrite the default machine folder if you don't like the spaces in the default name.

[gijobarts]

Storing the images along with the other VM info, combined with no longer needing to register images, is meant to make it easier to transfer VMS and their images to another host. I've been hoping they'd do something like this, as I use VB in a dual-boot system, and registering the image to another VM on the other OS causes problems when you forget to not use snapshots....

This way does make it a little awkward to share images between VMs, but I figure I'll just add a "shared images" folder on my install.

I agree with you on the whitespace, though. I don't know how much trouble it'd cause to change the default again, but as poetzsch said, you can change it on your system.