Click here to download Citrix XenConvert Application Software
Note: Citrix XenServer Conversion Manager is the preferred supported conversion tool for XenServer 6.1 and newer.
Identify the virtual machine you want to export.
Log on to that virtual machine and uninstall VMware Tools, as displayed in the following screen shot:
Note: You might experience issues if these items are not properly removed or uninstalled from Add or Remove Programs and from the Taskbar.
Delete any snapshots located with the virtual machine.
Delete any unnecessary data, drives, partitions, and applications that you no longer need for that virtual machine.
- Enable the automount feature for Windows virtual machines.
- If the Manifest feature in the VMware Workstation was enabled, delete the .mf file to allow importing.
Exporting OVF packages from VMware
The following VMware products support OVF export:
VMware vSphere 4
VMware Workstation 6.5.x
VMware OVF Tool 0.9 and 1.x
VMware Converter 3.0.3
VMware Converter 4.x
Note: The example shown here was done with VMware vSphere.
Select File > Export > Export OVF Template.
Select a Directory to store the OVF Export and in the Optimized for: field, select Web (OVF).
A dialogue appears indicating that exporting is completed successfully.
Copy the entire exported contents to your XenConvert workstation leaving the folder structure the same.
Converting OVF Export with XenConvert
- From XenConvert, select Open Virtualization Format (OVF) Package.
Note: OVF packages can only be converted directly to XenServer.
- Select the OVF Package to import and indicate whether you would like to Verify Content and/or Verify Author.
- Enter the hostname, user name (root), and password of the XenServer to convert the OVF package directly to.XenServer:
- Select Convert to start the conversion process.
Converting VMDK Files
Convert Vmdk To Ovf Powershell
Note: XenConvert is designed to convert a single virtual disk from VMDK format at a time. Copy data from all additional drives and partitions to an external location and delete any additional drives and/or partitions.
Browse the physical location of the VMware files and locate the virtual machine’s .vmdk file.
Make a note of the path to the vmdx file of the virtual machine.
Install XenConvert application on the Windows computer being used to perform the conversion.
Start XenConvert and select VMware Virtual Hard Disk (VMDK).
You are presented with the following options on converting a VMware Virtual Hard Disk (VMDK) for XenServer.
- XenServer option converts directly to an accessible XenServer host.
- XenServer Virtual Appliance option converts to an .xva format file that can be used to import.
- XenServer Virtual Hard Disk (VHD) option converts VMDK file to a .vhd file.
All the preceding options prompt you to browse for and select the .vmdk file to convert.
Option 1 – XenServer
Specify the destination XenServer hostname, User name, Password and Workspace to be used during the conversion.
Type or browse to the location where you want the converted files to be stored. For conversion efficiency, Citrix recommends specifying a location on the local computer where you are running conversion, preferably on a different partition or drive.
Note: The Workspace specified must have enough space available to convert the selected virtual machine.
Enter the name of the virtual machine, as you would like it to appear in XenCenter after it has been uploaded.
The XenConvert utility displays the progress of the conversion and uploading of the virtual machine to XenServer.
Note: Do not close dialogue box until the Status indicates “Conversion was successful!”
After the conversion process completes, XenServer shows the converted virtual machine by the name specified during conversion followed by “import”, as displayed in the following screen shot:
Option 2 –Xen Virtual Appliance
The Xen Virtual Appliance option converts the virtual machine into a portable format that can be easily moved, archived, or uploaded to XenServer.
After selecting the Xen Virtual Appliance option and VMDK file to convert you are prompted to select a folder to store the converted contents.
After the VMDK file is converted you have an output that lists an hda folder, ova.xml, .pvp and .vhd file.
Note: Do not change the file structure. The ova.xml file and hda folder must be on the same level.
Importing the Converted Virtual Machine to XenServer
Log on to XenCenter.
On the menu bar, go to VM > Import.
You have the option to browse for the ova.xml file or choose either Exported VM or Exported template.
Note: The same file extension (.xva) is used for both the exported virtual machines and exported templates.
Select XenServer Virtual Appliance Version 1 (ova.xml) from the Files of Type list. You are now able to browse and see the ova.xml file.
Select the XenServer host that you want to deploy the imported virtual machine to.
Select the storage repository where the virtual disks for the newly imported virtual machine will be stored.
Note: You can copy a Virtual Machine from one storage repository to another storage repository after the import process has completed. Refer to the Knowledge Center article CTX116685 - How to Copy a Virtual Machine From One Storage Repository to Another for more information.
Add the network interfaces you want to configure for the new virtual machine.
Click Finish to complete the import process.
Allow enough time for the import process to complete. The XenCenter Logs tab displays an estimate of the amount of time that the virtual machine takes to import.
The imported virtual machine will have the name “import” at the end of it to identify that it has been imported. You can rename the virtual machine after the import process completes.
Importing a Virtual Machine using the Command Line Interface (CLI)
Copy all the files required to a mounted share accessible by your XenServer host.
Run the xe vm-import command:
#xe vm-import filename=<path and name of ova.xml file> sr-uuid=<UUID of SR to install imported VM to>
Example: # xe vm-import filename=/nfs or cifs share/VMWare_WinXP_Export/ova.xml sr-uuid=da31c9d2-88ea-35f6-8c48-924db6c39817
CTX127641 - Citrix XenConvert Guide 2.3
CTX116685 - How to Copy a Virtual Machine From One Storage Repository to Another
Conversion from VMDK to OVF
The conversion of the VMDK file to OVF file is the process of changing the form of the presentation of the data, and not the data itself. Data conversion is a process performed for the requirement of the computer technology. We as end users are primarily interested in the substantive content of the file. The machines see the data in the files in a completely different way. They are not interested in the content. What they are interested in is the appropriate form or presentation of data, so that they could decipher its contents.
Despite the fact that the data are in the final form the strings of ones and zeros, they must be strings ordered in such a way as to be legible for a specific application or platform. Every time, when data is to be forwarded, they must be converted to a readable format for the next application - we are interested in the OVF output format. Data included in the VMDK file can be converted not only for the requirements of another application, but also for transfering them to another computer system.
Convert Vmdk To Virtualbox
Export and import of data and a manual conversion
Convert Vhd To Ovf Format
A data conversion is normally an automated process to some extent. The effect of the operation of one of the program is automatically the input for another application (some applications provide the possibility to automatically save the work done on the file VMDK file to the OVF format - EXPORT data). After exporting, you can easily perform IMPORT of the data in another application. If this is not possible, we can try to independently perform the conversion process from VMDK to OVF. To obtain a matched structure of the data, it is necessary to use an appropriate converter. A list of software to perform the conversion you are interested in can be found at the top of this page. File Converter - is a binary code translator compensating for differences in the code or making it a true translation, so that another machine or program understood it. For us, as users, the visible change will be only a different file extension - OVF instead of VMDK. For machines and software it is the difference between understanding of the contents of the file and the inability to read it.