Migration of servers to Proxmox VE - Proxmox VE

Migration of servers to Proxmox VEFrom Proxmox VEContents1 Introduction1.1 Windows systems specific P2V issues1.1.1 inaccessible boot device1.1.2 disk booting tips1.1.3 hidden nonpresent devices1.1.4 other suggested pages1.2 Fake Raid specific issues2 Physical server to Proxmox VE (KVM) using Clonezilla Live CDs3 How to migrate directly from a Windows physical machine to a VM raw file using SSH4 How to migrate directly from a Windows physical machine to a VM logical volume using NETCAT5 How to migrate from a physical machine to a VM, on a smaller partition5.1 main tool: fsarchiver5.2 mergeide5.3 running fsarchiver from SystemrescueCD5.4 backup the partition5.5 restore the partition5.6 successful cases6 Physical (running) server to Proxmox VE (KVM) using SelfImage6.1 Prepare the Windows operating system6.2 Prepare the Proxmox VE VM6.3 Do the migration7 Physical (running) server to Proxmox VE (KVM) using Windows backup7.1 The Workflow7.2 backup the physical machine7.3 creating a similar virtual machine7.4 restore the backup on the virtual machine7.5 reboot the virtual machine8 VMware to Proxmox VE (KVM)8.1 Prepare the Windows operating system8.1.1 Remove VMware tools8.1.2 Enable IDE8.2 Prepare the disk file8.3 Alternative migration using a rescue CD disk image8.4 Adapt the new KVM Virtual Machine9 XEN to Proxmox VE (KVM)10 KVM to Proxmox VE (KVM)11 Move OpenVZ containers to Proxmox VE12 Physical server (or KVM, VMware, XEN or other) to Proxmox VE OpenVZ Container13 Convert Windows to use SCSI (KVM)14 Physical (running) Windows server to Proxmox VE (KVM) using VMware Converter14.1 Prepare Windows14.1.1 Prepare location to save local image14.2 VMware vCenter Settings14.3 Prepare the VM on Proxmox14.4 Move the image to the Proxmox Server14.4.1 Using a USB Hard Drive14.5 Converting to qcow214.6 Final Steps

IntroductionYou can migrate existing servers to Proxmox VE. Moving Linux servers is always quite easy so you will not find much hints fortroubleshooting here.

Windows systems specific P2V issuesinaccessible boot deviceBooting a virtual clone (IDE) of a physical Windows system partition may fail with a BSOD referring to the problemSTOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)INACCESSIBLE_BOOT_DEVICE

this means that the source physical windows machine had no support for IDE controller, or at least the one virtually replacedby kvm (see Microsoft KB article (http://support.microsoft.com/kb/314082/en-us) article for details): as Microsoft suggests,create a mergeide.reg file (File:Mergeide.zip) file on the physical machine and merge that in the registry, 'before the P2Vmigration. Btw, it may not be necessary but should be no harm, anyway, and save you lots of time and headaches.Windows 2000: see [1] (http://www.motherboard.windowsreinstall.com/problems.htm)disk booting tipscheck that your disk has "boot flag" enabled (you can check this with gparted, on ntfs disks, booting the vm from alivecd iso, see this gparted manual page (http://gparted.sourceforge.net/docs/help-manual/C/gparted.html#gparted-fix-operating-system-boot-problems) ) maybe not so windows-specific but better remind it here.be sure that boot.ini on your system partition is still suitable to your current disk/partition configuration (see thiskb article (http://support.microsoft.com/kb/124550) and this kb article (http://support.microsoft.com/kb/102873) )

hidden nonpresent devicesIf your source physical machine had network interface controllers (nics) with static IP assigned and then you clone the systemto a vm, you will need to add a virtual ethernet controller, provided by kvm, but Windows won't let you assign the same fixedIP to the new virtual nic, because (it reports) there is a hidden and nonpresent devices already configured with the same IP(see Microsoft KB article (http://support.microsoft.com/kb/241257) ).

For sure it should be removed from windows "known" hardware but, you won't find it in "device management", even if you specify"show hidden peripherals", why? because Microsoft is complicated :-)

To be able to see, and then remove the old physical nic from "device managemnt", you have toopen a console windowtype:

set devmgr_show_nonpresent_devices = 1and press enterthen, in the same console (do not close it) type:

start devmgmt.mscand press enterthis will open the same "device management" panel you could have open from the "control panel", but now if you set the"show hidden peripherals" flag, the "nonpresent" devices will appear, although dimmed somehow, and you will be able toremove them, freeing the IP for your virtual nic.