I consider this a bug, and hope it can be addressed in a future release.
Running VirtualBox 4.2.6 on OpenIndiana 151a7:
Is this a good place to report something as a bug, and see it have a bug ticket
created?
Normally, up to and including 4.1.x, I create a new zfs filesystem for each
virtualbox guest.
sudo zfs create virtualmachines/foomachine
And then go into Virtualbox, and create a new machine named "foomachine"
But, I just upgraded to 4.2.x, and the new behavior is, if a directory already
exists, virtualbox refuses to allow you to create a new machine in that
directory. It says "Cannot create the machine folder foomachine in parent
folder /virtualmachines"
The workaround, at present, is this:
Don't zfs create before creating the new machine.
Start by creating the new machine, with no hard drive. This will create the
directory, with .vbox file in it, only.
Close VirtualBox.
Now rename the directory "mv /virtualmachines/foomachine
/virtualmachines/foomachine_temp"
zfs create virtualmachines/foomachine
mv /virtualmachines/foomachine_temp/* /virtualmachines/foomachine/
rmdir /virtualmachines/foomachine_temp
Launch VirtualBox, Edit your machine and add a virtual hard drive.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:
mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
