We need another directory to store a working copy of our virtual machine. However, since svn stores the data in the repository in its own internal format, we cannot access it directly. The repository we created in /vm/repo/Fedora will hold all the snapshots of our virtual machine. Assuming our repository will reside in /vm/repo/Fedora, we make sure the directory /vm/repo exits and then execute svnadmin to initialize an empty repository: To keep track of changes we make to our virtual machine, we first need to create an svn repository. Use at your own risk! Preparing the repository and a working copy This means you may easily lose your data if you don't know what you are doing. If you intend to use this method for jumping back and forth in time between your virtual machine snapshots, you will most probably run into conflicts while trying to commit some of your changes with svn.
Vmware player snapshot how to#
In the rest of this article I will briefly demonstrate how to do it with svn using an example Fedora virtual machine on one of my Linux boxes.Ī word of caution: Please note that this is not a commercial one-click solution for all your problems. It is, however, very easy to implement VMware Player snapshots using a source code management system, such as Subversion or git.
It is true that VMware Player doesn't offer this functionality by itself, because VMware sells this in their commercial products. The usual answer to this question is “no”. I've seen numerous posts on the web by people asking whether it is possible to keep multiple virtual machine snapshots with VMware Player.
0 kommentar(er)
