virtualbox.org

Hi,
I use linked-clones for demo/testing purpose. I use this method because it allows me to save hdd space when working under the same OS architecture.

The question is, if it is possible to merge the linked-clone disk (snapshop of the base) with the base vhd so that it becomes 1 virtual disk file.


On top on this question, when I was looking for a way to achieve this, I was looking to the base vm snapshots section, and I can see all the snapshots associated with this VM, and when I create a linked clone the correct snapshot to allow the cut off point.
The snapshot interface has a hierarchical way to display information. When I read it I see:
Linked Base for xxx and xxx1
Linked Base for xxx and xxx2
Linked Base for xxx and xxx3

Should not the cut off point be always at the same level as the first snapshot? The fact that its under the next snapshot it looks like its using the loned vm snapshot to create the cut off point for the next one.


This might be just graphical, as I know this i working correctly...
I hope I was confusing in my 2nd question... it can sound confusing when I read it back...

Just create a full clone (of current state) from the linked clone.

One thing: don't fixate on cloning the disk. Clone the VM, and let VirtualBox take care of deciphering file structure and diciding what components of the VM to clone.

I know this is a super old question, but I came across it when searching for an answer to the same question. As it turns out, for me the solution was just to remove the base virtual machine from within the VirtualBox Manager. When prompted, select "Remove only" so that you retain the files that the new linked machine still relies on. Obviously this is only a good solution if you are not planning on using the base machine anymore. I used this approach when testing out a new configuration and wanted to do it in a safe environment. More specifically, I created a linked virtual machine so that I could update my Ubuntu machine to the latest Long Term Support version. This can be a little tricky, and I needed to be able to continue to do my work on the old machine until I knew that the new machine could handle the upgrade. This turned out to be a great way for me to tweak the settings on the new machine while being able to have the "old machine" open and running, in case I needed to use it.

I'm not sure what problem that would be a solution to? It doesn't give you a stand alone offshoot VM, so all of those fragile dependencies are still there.