Cloning

This is for discussing general topics about how to use VirtualBox.
Post Reply
JGH
Posts: 3
Joined: 6. Dec 2013, 19:51

Cloning

Post by JGH »

Hello,

I am using Virtual Box 4.2.12 r84980 in a windows environment.

What I am trying to do: I have begun to create several machines that are in various stages of our install process. Meaning, each machine has different components at a specific stage of install (ie machine 1 with operating system + sql, machine 2 with operating system + sql + software application). I felt this was a more efficient way to have stages ready pending what needs to be emulated/created. The alternative had been to start from the beginning each time to build a machine.

How I did it: I referenced an article on cloning in order to create my different stage machines. I wanted to use the most recent machine, clone it and then bring it up to the next stage before cloning it again. That way each machine is the same but unique. The article was found at techrepublic with the subject of clone-and-move-virtual-machines-in-virtualbox

My Issue/ Concern: In the article it references to copy the clone to an external or shared drive since the process creates the clone on my C drive. After the clone has been copied and moved, the article asks to create a new machine by pointing at the newly copied files (which, by the way, are not .vdi flies but .vbox and vmdk). However, when you go through the clone process it automatically creates a machine pointing at the c drive files in the virtual box rather than allowing you to create your own, pointing at the newly copied files on your external drive. My concerns are twofold. Since the machines are all pointing at the files on my C drive, I am concerned about running out of room down the road. Secondly, can you (or should you try to) point the newly created machines at the copied files on the external?

I am open to any advice of the questions above and also advice if I should be creating machines in a different way.

Thank you
noteirak
Site Moderator
Posts: 5231
Joined: 13. Jan 2012, 11:14
Primary OS: Debian other
VBox Version: OSE Debian
Guest OSses: Debian, Win 2k8, Win 7
Contact:

Re: Cloning

Post by noteirak »

Cloning will use the default Machine folder that is set on the global Virtualbox config.
You should change that if you want the clone to go somewhere else.
Hyperbox - Virtual Infrastructure Manager - https://apps.kamax.lu/hyperbox/
Manage your VirtualBox infrastructure the free way!
JGH
Posts: 3
Joined: 6. Dec 2013, 19:51

Re: Cloning

Post by JGH »

Excellent. Thank you for the feedback. I will make that adjustment going forward. Do you know if you can 'point' the machines already created to a different location? The Advanced tab of the general settings hints that it is possible but not sure of any repercussions. Thanks again.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Cloning

Post by mpack »

JGH wrote:Do you know if you can 'point' the machines already created to a different location.
Howto: Moving a VM.
JGH
Posts: 3
Joined: 6. Dec 2013, 19:51

Re: Cloning

Post by JGH »

Are there any issues changing the default machine folder location to that of an external hard drive? I thought I had read somewhere that it could be an issue with windows.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Cloning

Post by mpack »

The question is rather vague. Changing the machine folder for new VMs will have no effect on existing VMs. If you're asking what the downsides are of locating VMs on a removable drive then the issues I can think of offhand are :-
  • The portable drive is often slower. In the case of a USB2 drive the poor performance may make the VM unusable.
  • VirtualBox stores the path to the VM folder. Windows hosts may reassign drive letters at any time, invalidating VBox's stored path.
  • There is a danger that you'll absent-mindedly unplug the drive while the VM is running, resulting in a corrupted VM disk and possibly a corrupted VM control file.
Post Reply