Jens Franik wrote: > Guten Tag Chris G, > > am Sonntag, 15. Februar 2009 um 13:33 schrieben Sie: > > >> I guess mine are mostly at default so it didn't seem like all that >> much to set up. :-) >> > > Same here, but if this is important, i guess one can easy write a Copy > export import for the XML, so only one time to do the work :-) > > I wrote a script to clone a "template" VM which copies the VDI, then uses "VBoxManage -nologo showvminfo <vm-name> -machinereadable" to extract the settings of the original VM as a <key>=<value> list. If you redirect the output of that command to a file you can read it in as a set of variable definitions in a bash shell, and then use appropriate VBoxManage commands to create and set-up the new VM as a clone.
I would post the content of my script, but a lot of it is project-specific and some commercially sensitive. But using the "showvminfo" command avoids hacking the XML, for sure. _______________________________________________ vbox-users mailing list vbox-users@virtualbox.org http://vbox.innotek.de/mailman/listinfo/vbox-users
