Young schrieb:
Antonio Augusto (Mancha) wrote:
On Thu, Jun 4, 2009 at 22:08, Young <[email protected]> wrote:
Is there a way to control which snapshot version is cloned?
My one successful cloning resulted in the earliest version of the image,
which would be a major pain, if not entirely useless.
You should clone the actual snapshot disk (located under
VMName/Snapshots) and not the "real" disk image.
This way always worked for me.
Yes, just specify the uuid instead of the name. Much less typing :)
However figuring out the UUID isn't entirely easy. The easiest way
probably is
Thanks for helping Antonio.
That's helpful information, and it should be in the documentation.
The problem with documenting this is that it'll be extremely difficult
to understand. The snapshot name makes sense only in combination with a
VM name (several VMs may have the same snapshot names), and even if both
bits of information are available it's still not unique enough: a VM can
have up to 32 disks, and thus the base name of the image you want to
clone is also necessary.
Any good ideas how to implement this in an easy to use fashion are
highly welcome. At the moment I can only think of adding further
(optional) command line parameters for the VM name and snapshot name,
and let VBoxManage do the walking.
That doesn't cover esoteric cases such as using the same image as
several disks (yes, that's possible, read the manual).
But, in the snapshot directory the file names do not correspond to the
snapshot name. The only way to relate them seems to be the date.
But, every file that corresponds to the date of a snapshot has a .sav
file extension.
The .sav file is not related to disks. They contain the state of the VM
when the snapshot was created.
How does that work? Isn't a .vdi file extension required?
Strictly speaking the .vdi file extension is never required, but you're
looking at the wrong files.
Klaus
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
