V2p

sketch > win > V2P

- WMVare converter
5letek innen:
http://sandbox.fortechitsolutions.ca/pmwiki.php/Assorted-Reference/Vmware-to-kvm-proxmox-migration

Hi Dave,

As I said in my post, the machines I migrated last week with Clonezilla were not 'real physical hosts'. They were VMware based VMs running on ESXi 3.5 I believe. But - the process is the same - a VMWare VM (or a ProxVE KVM VM; or a Xenserver Xen based VM) - are all a "standalone system" in their own right; and would all be equally migrated via clonezilla.

You are correct, you need to boot the 'source' system from clonezilla to migrate it. This implies either
(a) remote KVM console control of the server being migrated, configured and working, OR
(b) physical access to the server, console, optical drive which boots the server (or USB bootable device - memory stick - appropriately prepared and tested)

so - it is an 'offline' migration - in the sense that you reboot your windows host to Linux/Clonezilla
Then capture data using clonezilla and send 'image of hard drive' to a nearby SSH:NFS:SMB server / storage pool
Then boot your target system (ProxVE KVM VM instance) using clonezilla liveCD (iso)
Then restore from your SSH:NFS:Smb server which has the "image of hard drive" for system being migrated
Then once clonezilla restore is done, you can reboot the ProxVE KVM instance, and bouf, it will spin up.

If you want a non-offline approach I know of a few other options I've used,

- Citrix XenServer distribute a free tool that facilitates migration of a server to a Xen VM image file.
- I've used this tool in the past to build a VM image of a host; then copy this image file over to ProxVE; then use qemu-convert tools to flip it to a more desirable format; and ProxVE was able to boot it.

The main constraint I had in this sort of conversion, is that you need to have a second storage device available to hold the image data file.

For example (simplest scenario), if you have a Win2003 physical server with a single C: drive of 100gig
Then you need either (a) second hard drive - even a crummy USB disk is adequate or (b) a SMB storage target that is tolerable performance (gig ether, not a cruddy NAS device ideally) - which is accessible from the 2003 server being migrated.

Then you run the XenServer migration tool; tell it to store the output ~100gig system image file on your 'non-C-Drive storage device' and let it grind. It takes a while; longer if your storage is slow (USB / cheapo NAS / etc rather than internal SATA /SAS/Direct-attached / Raid device) but it does work.

VMware P2V (free) migration tool also works but is a 2 step process, and is better to avoid because it installs VMWare tools in the migrated VM; which you then have to uninstall before migrating - ie - a 2 step migration, extra work:drama.

There are commercial tools which also cook image files but these are not free of course

Tim


I assume(?) you have run the "mergeide.reg" on the system before doing this? if you fail to do ths step, then likely windows can't boot from the image in the KVM environment - this forces it to have IDE drive support, which is needed to boot 'the first time'. After that you can go through process of forcing install for Paravirtual IO drivers; change over to paravirt for HDD - and get better performance for the VM disk. But the first boot, you must have IDE support or the migration is dead in the water.


Reactivate:

All you need to do is reset windows config with the sysprep tools:
http://technet.microsoft.com/en-us/library/cc721940%28v=ws.10%29.aspx


disk2vhd (virtual hard disk, ms own format):
http://technet.microsoft.com/en-us/sysinternals/ee656415

Online-ban is meg tudom csinalni.

you just need to convert the generated vhd file to raw or qcow2, with "qemu-img convert"


KVM+Qemu tutorial
http://blog.falconindy.com/articles/build-a-virtual-army.html

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-NonCommercial-NoDerivs 3.0 License