ONE HUGE EXAMPLE....
You are running an OS and you run a VIRUS SCANNER... You update the virus scanner & there is a BUG that kills off you rebooting back up & you are left with going to see the computer tech...
[Which actually did happen a few yrs ago with one virus software vendor's update]
NOW using cloning with VIRTUAL MACHINE you could have 2 or more of them and update one and if there is a BUG you could just delete the messed up clone that you updated & with the BUG it messed up your new clone... THUS you deleter the clone & fire up one of the other clones you created BUT DID NOT UPDATE YET.... And maybe wait until there is a fix for the problem that when you update the bug messed up the OS... AND save yourself the big huge tech visit & shelling out hundreds of $$$ for a El-quick computer fix...
Discussion on:
View:
Show:
I have tested and rollbacked changes such as OS updates to a VM (Windows 7) and have used the VM Snapshot for this purpose. The advantage of this over cloning is that it is quicker to create/save, and you can load the Snapshot state before the changes. I have similarly used cloning to troubleshoot problems with a VM to see if it was somehow corrupted or start out with a clean slate. A disadvantage of the snapshot is that you have to manage different ones and clean them up over time by deleting or merging them and this may take as much time to do this as it would to create a clone. Both options are useful depending on what you are trying to do.
I've been wanting to clone some virtual box images from one PC to another but didn't know if it could be done. Thank you.
If you copy the entire folder that contains the clone into the VirtualBox VM directory on the destination machine, you don't need to create a new VM and point it at the associated .vdi since it also has the configuration settings for the VM in the .vbox file. Move the entire folder for your third step and fire up VirtualBox on the desintation machine. It will already see the new (cloned) VM in the folder and populate the list of available VMs appropriately.
Easier is to just copy the *.VDI image (either way you need to copy the file to other location anyway) with any file manager like Windows Explorer then run the VBoxManage command to change the UUID.
VBoxManage internalcommands sethduuid VMName.vdi
VBoxManage internalcommands sethduuid VMName.vdi
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
