VirtualBox allows us to copy a virtual machine from one host to another easily. You just copy the hard disk file (usually .vdi or .vhd) to the new host. Then you use the transferred hard disk file to start up a new virtual machine on the new host. That’s it! However, I have found that if you use this method on a VM containing snapshots, you only get an old machine state of the original virtual machine. All saved snapshots are lost. In this tutorial, I explain how to move a VirtualBox VM to a different host and still retain the snapshots on the original host.
Developers often need to set up sandbox development environments where they have full privileges to manipulate stuff. Here, I summarize the steps for setting up a SharePoint development virtual machine (VM). This article focuses on the nuances of installing SharePoint Server 2013 SP1 On Windows Server 2012 R2.
VirtualBox is a cross-platform virtualization application. It installs on your existing computer (and operating system) and extends the capabilities of your existing computer so that it can run multiple operating systems (inside multiple virtual machines) at the same time.
At the end of my previous post Moving A VirtualBox VM With Snapshots, I described a common VirtualBox error you may experience when you try to clone virtual machines and move them around. The error is associated with VirtualBox Guest Additions which is usually installed across individual virtual machine instances.
This article goes straight to the installation and VM setup process. We shall be creating a Windows Server 2012 VM on a Windows 7 host machine. For some more background info, See my previous post – VirtualBox and Virtualization: An Introduction.