VM Migration XEN to VMware

By 5 June 2021 June 22nd, 2021 No Comments

Recently I had the possibility to work with VMs running Xen App, especially on XEN. One request from the customer was the possibility to move the VMs from XEN to VMware without reinstalling everything, so porting a part of existing infrastructure and VMs into VMware. I spent quite a lot of time finding the proper procedure that avoids the issue to the VMs when moved to VMware related basically to a lot of BSOD based on dirty XEN drivers mainly related to the SCSI controller.
Long story short I’ll put here the procedure (this procedure is not supported from VMware or XEN, so use it at your own risk):


– Remove VM on the Citrix Farm, Disable app published on a specific server

– Shut down the VM on XenCenter

– Clone it

– Power on the clone, and took a snapshot

– Uninstall Citrix XenServer Management Agent

– Uninstall Citrix XenServer Windows Guest Agent

– Uninstall Citrix Xen Windows x64 PVDrivers

– Uninstall Citrix XenServer Tools Installer

РLaunch from: Program Files x86 Citrix  XenTools Рunistall-Xenprovide

– Device Manager: Uninstall all XEN Drivers for Disks, Network,Controllers, CD/DVD Drives, Hidden Devices (NO REBOOT)

– Check the Devices

– Remove if present RegKeys HKEY_LOCAL_MACHINE/SYSTEM\CurrentControlSet\Services\XEN \xenbus \xenvif \xendisk

– Remove if present RegKeys HKEY_LOCAL_MACHINE/SYSTEM\CurrentControlSet001\Services\XEN \xenbus \xenvif \xendisk

– Remove if present RegKeys HKEY_LOCAL_MACHINE/SYSTEM\CurrentControlSet002\Services\XEN \xenbus \xenvif \xendisk
– Remove if present RegKeys HKEY_LOCAL_MACHINE/SYSTEM\CurrentControlSet\Control\Class – check if there is a key with upperfilter XEN*

– Remove if present RegKeys HKEY_LOCAL_MACHINE/SYSTEM\CurrentControlSet001\Control\Class – check if there is a key with upperfilter XEN*

– Remove if present RegKeys HKEY_LOCAL_MACHINE/SYSTEM\CurrentControlSet002\Control\Class – check if there is a key with upperfilter XEN*

– Remove from C:\Windows\System32\Drivers\Xen.sys-xenbus.sys-xencrsh.sys-xendisk.sys-xenfilt.sys-xennet.sys

Then you can Reboot

Once the VM is back you can install vCenter Converter, if you don’t have it you can download it free from the VMware site.
I highly recommend if you have it running on your system to stop the following Citrix Service: Citrix System Monitoring Agent service

Also if needed I recommend to increase the timeout for the service start, vCenter Converter creates the following regkey on:


ServicesPipeTimeout   = 300000

Reboot, check again if the Citrix System Monitoring Agent service is stopped and then start the conversion, wait of course al the vCenter Converter services are running (this will require based on the server 5 to 15 minutes)

Then you can start the migration of your VM with vCenter Converter

I hope this could be helpful if you have questions or you want to add your own procedure please write a comment!

Giovanni Dominoni

About Giovanni Dominoni

Leave a Reply