Hi, Mark. I have seen that you also sent a couple more posts, and I will read them as well and reply if need be, but taking these in each at a time, I want to respond just to this one right now. Incidentally, my intention is not to run more than one instance of this Vista OS simultaneously, neither in the same "Host/VBox Installation" nor in any other sort of combination.
My goal is simply to have two different installations of the same Vista OS, which will not be run simultaneously but could be run, preferably (but not necessarily), on the same "machine/host/VBox installation"; or, if that is not possible, then I would like to run one of them on "machine-1/host-Windows7/VBox installation A" at one time, and at a different time to run the other one on "machine-1/host-Linux/VBox installation B". If I can get either one of these two combinations to work without having to re-activate the Vista OS, then I could work out any other machine/host combination likely to be needed. > -----Original Message----- > From: Mark Cranness [mailto:[email protected]] > Sent: Sunday, October 28, 2012 5:42 PM > To: Community mailing list of VirtualBox users > Subject: Re: [VBox-users] cloning and Windows activation > > 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). If I understand your meaning here, it is to have one instance of Vista on machine-1/host-A and to have a second instance of the same Vista OS on (same) machine-1/host-B. Is that correct? Yes, this would be a multiboot machine. > 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. > > ----------------------------------------------------------------------- ------------------------------------------------------------------------------ The Windows 8 Center - In partnership with Sourceforge Your idea - your app - 30 days. Get started! http://windows8center.sourceforge.net/ what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
