On 29 October 2012 11:17, John A. Wallace <[email protected]> wrote: > When I > open the VBox Help file and use its Search tab to look for either > "internalcommands" or "sethduuid", it fails to find them.
"internalcommands" means largely undocumented, which is why they aren't in the help file (although the 4.1.18 PDF help does mention some of internalcommands commands). Use "VBoxManage internalcommands" to get some help on those. internalcommands won't help you if your intent is to run the two VMs on the same host instance. internalcommands sethduuid can set a different UUID, but the cloning process already does that. internalcommands sethduuid can set the SAME UUID, but a simple file copy already does that. If you use a COPY (rather than a clone), and run the two copies on different host instances, then that would work. VirtualBox installed on HostA running Linux and VirtualBox installed on HostA running Windows are different hosts (but you have to reboot the host). Possibly VirtualBox installed on HostA logged in as user A and VirtualBox installed on HostA logged in as user B are also DIFFERENT hosts, because the ~/.VirtualBox/VirtualBox.xml file is separate for those (AFAIK). I'm not sure how the VirtualBox services/daemons work in that case, but logging in as a different users might let it work, if the users have different ~/.VirtualBox/VirtualBox.xml files. ------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
