Citrix XenConvert is a tool to migrate (P2V) physical (or virtual) Windows systems to XenServer.

XenConvert is similar to VMware Converter but without some of the advanced features and functions. XenConvert is installed and executed on the source system and only one local disk can be converted at a time. You must have 115% free space to convert a disk, the free space does not have to be on the same local disk, but it cannot be a mapped network drive.

XenConvert creates a local VHD file, mounts it as a new drive and then copies the contents of the local drive you are converting to the new VHD file. If during the XenConvert wizard you chose to migrate to XenServer, it then takes the VHD and creates an XVA (XenServer Virtual Applicance) and then moves it up to the XenServer and creates the new VM. The process takes at least twice as long as it does with VMware Converter. Most of this time is spent copying the local disk to the local VHD file. XenConvert does not have a feature that lets you resize the destination VHD, if your local disk is 72 GB then the virtual disk will be 72 GB. Some other features of XenConvert include the ability to convert an offline VMDK to either a VHD or OVF and Microsoft VMs to OVF.

how to use xenconvert

xenconvert supports: physical to VHD, physical to XVA, physical to XenServer. The preferred conversion method is to OVF. As this will capture metadata about the machine. Install the xenconvert tool onto the server to be converted. At the prompts enter the information the wizard is requesting; From: name of this machine you are on. To: Open Virtualization Format {OVF} package. Choose the volumes to include in the conversion from the drop-down menu. Choose a folder to store the OVF package in by typing or browsing to the location. Optional: choose a EULA to include in the OVF package by typing or browsing to the location. Optional: edit the name of your new VM in the Name textbox. Optional: check the Log name of converted files checkbox to log the name of each copied file to xenconvert.txt. The log file is located here %systemdrive%\Program Files\Citrix\XenConvert\xenconvert.txt Verify the conversion information is correct, then click Convert The conversion is complete when the progress bar reaches 100% and the status field indicates that if the conversion was successful or not. Click Finish to exit XenConvert, or click Log to display the conversion log file.

Now we need to import the OVF file we made into XenServer. Open XenConvert again. At the prompts enter the information the wizard is requesting; From: Open Virtualization Format {OVF} package. To: XenServer. Browse for the OVF file to include in the conversion. Optional: Verify Content - verifies the content in the manifest at conversion time. Optional: Verify Author - verifies the author is the source of the manifest at conversion time. Next XenConvert checks if the OVF package is encrypted. This can take some time so be patient. Next provide the following information for the conversion to progress; Hostname: simple hostname, fully qualified domain name or IP address of the XenServer. Username: name of the account with import privileges. Password: use password that is associated with the above username. Verify the conversion information is correct, then click Convert The conversion is complete when the progress bar reaches 100% and the status field indicates that if the conversion was successful or not. Click Finish to exit XenConvert, or click Log to display the conversion log file

If you are in a hurry another option is to use ShadowProtect to take an image of the drive. Then create a new XenServer Virtual machine, and keep the HDD size the same as the source, and then use ShadowProtect to restore the image to the HDD of the new Virtual Machine. I’ve done this before and it will require extra tweaking but is a valid option.

xenconvert notes

XenConvert does not effect the power state of any currently running VMs during a conversion or import. Regarding virtual hardware dependencies, XenConvert automatically checks for sufficient free space before the import, and XenServer automatically checks for sufficient free RAM before powering on VMs. Windows Server 2003 x86 needs SP1 installed for XenConvert to work/start. Disable virus scanner and Disable any hardware Specific software before starting a conversion.

Posted in Andruku.com

http://www.youtube.com/watch?v=MPeow8EzgiI

XenConvert 2.5 Guide from citrix is available here.