Requires Membership to View
To gain access to this and all member only content, please provide the following information:
By submitting your registration information to SearchVirtualDataCentre.co.uk you agree to receive email communications from the TechTarget network of sites, and/or third party content providers that have relationships with TechTarget, based on your topic interests and activity, including updates on new content, event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile, unsubscribing via email or by contacting us here
- Your use of SearchVirtualDataCentre.co.uk is governed by our Terms of Use
- We designed our Privacy Policy to provide you with important disclosures about how we collect and use your registration and other information. We encourage you to read the Privacy Policy, and to use it to help make informed decisions.
- If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States.
Even the cross-hypervisor P2V conversion tools -- such as PlateSpin Migrate, and my underdog favorite Vizioncore Inc.'s vConverter -- do not support VirtualBox as a destination hypervisor. Strangely, while hypervisors typically produce a conversion tool, VirtualBox has not. Despite these obstacles, fear not -- there is a way.
It all starts with a Virtual Machine Disk (VMDK)Last year, I blogged about importing VMDK into VirtualBox -- a key part of converting physical servers to VirtualBox VMs. The process also requires VMware vCenter Converter, but there are a few steps involved. Here I will cover a typical P2V conversion scenario involving a Windows Server 2003 system. First, install vCenter Converter (standalone or local edition) on a Windows system. This can even be installed on the Windows Server 2003 system you're converting. Usually, I designate one system as a "launchpad" for conversions. Once installed, launch the convert virtual machine task. The next screen will ask what server you want converted. For this article, the server I am converting is named Baselinews2k3.
Figure 1
The wizard allows you to select an appropriate destination virtual format. (Click image for an enlarged view.)
(Note: If you have used vCenter Converter to convert VMs to formats in VMware Infrastructure 3 or vCenter, these steps will differ from what was done previously.)
For VirtualBox to use the converted system, it needs direct access to the VMDK files. The easiest way is by selecting a non-ESX or ESXi virtualisation format. In this example, I use the VMware Workstation format.Figure 2
This shows the test server moving from a VMware Workstation format to a remote file share. (Click image for an enlarged view.)
Figure 3
Options such as automatically installing VMware Tools should be skipped, because the ultimate goal is to create a VirtualBox machine. (Click image for an enlarged view.)
Figure 4
The Virtual Media Manager is accessed within the VirtualBox file menu.
(Click image for an enlarged view.)
Figure 5
Create a new VM and name it. (Click image for an enlarged view.)
Figure 6
Here, you can assign the VMDK that were added into Virtual Media Manager. (Click image for an enlarged view.)
Figure 7
This is done in the VM properties.
(Click image for an enlarged view.)
- You may have to architect a storage solution to meet your needs.
- Operating system storage drivers and devices are your best bet to get a workable storage system in place.
- VirtualBox does not offer a clustered file system, such as VMware's Virtual Machine File System or Microsoft's Clustered Shared Volumes.
- Some advanced options with Sun storage may be available for VirtualBox, such as Sun Storage 7000 Unified Storage Systems.
Rick Vanover (vanover-rick@usa.net), VCP, MCITP, MCTS, MCSA, is an IT infrastructure manager at Alliance Data in Columbus, Ohio. He is an IT veteran specialising in virtualisation, server hardware, operating system support and technology management.
This was first published in November 2009