The Virtualization Room

A SearchServerVirtualization.com and SearchVMware.com blog

» VIEW ALL POSTS Jul 1 2008   12:05PM GMT

Importing VMDK disk files into Sun xVM VirtualBox



Posted by: Rick Vanover
Tags:
Rick Vanover
Sun xVM
VirtualBox
Virtualization
Virtualization platforms

Sun xVM VirtualBox for Windows offers the capability to import VMware-based VMDK files into a virtual machine (VM), making a migration or cross-platform deployment quite enticing. VirtualBox 1.6.2 does not yet support the Open Virtual Machine Format (OVF) implementation; however, native handling of the VMDK files will suffice for most situations. Let’s go through importing a VMDK file for use in VirtualBox.

The critical tool in VirtualBox is the Virtual Disk Manager (VDM) for disk access. For most of us with a VMware-centric background, this will be a new concept. The VDM is a single tool where all virtual disks are inventoried. This can span multiple locations as well as multiple disk types – such as floppy, CD-ROM, and hard drives. Further, for the hard drive inventory, it is ubiquitous as to whether the disk is a VMware VMDK file or a VirtualBox VDI file. The figure below shows the VDM with an inventory of both VMDK and VDI files:

VDM View

When a VM is created (or when modifying and existing VM), the drive inventory can be specified to create a new virtual disk or use a disk that is listed in the VDM inventory. By managing the virtual disks within the VDM, the VMs can pull directly from this inventory based on your configuration. The VDM can provide disks of all types from remote locations, such as a UNC path or a mapped drive.

There are a few important notes on the use of VMDK files within VirtualBox. First is that the snapshot functionality is not yet supported for VMDK files within VirtualBox. Second, if you intend to boot from the VMDK file, the VM may need boot device modifications. And lastly, the VMDK is modified when used by VirtualBox, so if you go back to using it with a VMware product, depending on what you have done to it – it may not be accessible. For non-boot drives, this should be a transparent exchange.

More information on the use of VMDK files within VirtualBox can be found in the online user guide for VirtualBox in section 5.4.

4  Comments on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Rick Vanover
    Hi, I imported the .vmdk Windows guests' hard disks, but didn't manage to boot them (I only got black screen). Could you please tell what are the "boot device modifications" that I need to implement? Thanks -- rob
    0 pointsBadges:
    report
  • Rick Vanover
    Rob - You may need to "repair" the installation using the installation CD (or other medium). The repair process strips out any previously known hardware config from the Windows installation, and "detects" the VirtualBox hardware. Your software should continue to work after this repair process.
    0 pointsBadges:
    report
  • Rick Vanover
    I'm using version 2.1.0, It could add a vmware virtual machine and boot from it in Virtual box without modifications. However the first time, the X server could not start, it just asked me to enter the root password to reconfigure it, and then it worked.
    0 pointsBadges:
    report
  • Silverface1980
    @rob you have to check the settings from the source and before you run the newly imported .vmdk. configure the settings in the destination with the same settings it has from the source. such as system, storage, display and so on...
    10 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: