WARNING: Underwater stones of VirtualBox: (VBoxSVC and *.vbox meta-data) VBoxSVC is a service that controls all VMs. One such service runs per-host/per-user, and VBoxSVC has a nasty habit of over-writing all VM meta-data on process exit, and god forbid you have 2x VBoxSVCs running (from different hosts). It may wipe out VM's meta-data, making the VM unbootable.
To combat this: Make sure only one VBoxSVC runs (it must be shut-down on the inactive host). Also make sure to backup the VM meta-data by your script. It sits inside *.vbox files. This is necessary if you make *any* change to the VMs during runtime, such as adding shared folders, or adding snapshots. If you make *no changes*, it is not necessary. NOTE: To share VMs like that, it requires, that the VMs are *created* by VirtualBox v4+ (v4.0.x or v4.1.x or newer) -- -Alexey Eromenko "Technologov" ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
