If considering moving a virtual machine (VM) from one virtualization platform to another, you might want to think about just creating a new VM on the preferred platform. However, if you would rather avoid a complete reinstallation and are interested in trying a VM migration, then read on to find out some tips on making the move as smooth as possible.

In the blog entry Migrating from VMware to VirtualBox: Oracle Enterprise Linux, author The Fat Bloke describes a couple of rules of VM migration and provides four steps in making the move from VMware to VirtualBox easier.

As alluded to earlier, the first rule of VM migration offered is don't. It is suggested that starting from scratch on the new virtualization platform will save users the possible trouble of the guest operating system not reacting well to the different virtual hardware. Additionally, some software installed above the OS, such as VMware Tools, may be relying on specific virtual hardware.

But for those determined to migrate, the example used in this blog supposes the Oracle Enterprise Linux as the guest OS that is to be moved to VirtualBox 3.1 from VMware Workstation 7.

The Fat Bloke's second rule of VM Migration is that it is easier to unpick platform-specific software on the native virtualization platform and he demonstrates this in the midst of the first step: Preparing to Migrate, which involves removing VMware tools, resetting the Display and Input device configuration, and removing incompatible devices.

Step 2 covers exporting the VM with details on configuration information (in VMware a .vmx file) and virtual hard drives, which the guest is installed on. (typically .vmdk files).

Step 3 goes into importing into VirtualBox and verifying Oracle Enterprise Linux boots up under it.

The final step is installing the VirtualBox Guest Additions, which, once mounted, can install from the mounted directory using the command:

sh VBoxLinuxAdditions-x86.run

A screenshot is shown here, as well as through each of the steps.

The Fat Bloke also offers an alternative for steps 2 and 3 for more advance users. He advises to simply take the VMware disk image (.vmdk) and plug it into a manually configured VirtualBox vm. This effectively relies on the user to create an appropriately similar vm instead of relying on the ovf export and import (Steps 2 and 3 above) process. It should be noted that the default disk controller used by VMware is an LSI SCSI controller, so when manually creating a VirtualBox vm you need to configure it appropriately, he writes.

More Information

Migrating from VMware to VirtualBox: Oracle Enterprise Linux - The Fat Bloke's blog entry

VirtualBox 3.0 - Worthy Competitor Against VMware Workstation, VMware Fusion

Sun VirtualBox 3.1

How-to Setup VirtualBox and Create Virtual Machines

VirtualBox Joins Oracle's Enterprise Virtualization Portfolio [...read more...]

		fullsource
Print Email Current Profile Archive Blog Generate newsletter